All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Matt Carlson" <mcarlson@broadcom.com>
To: "Ben Hutchings" <ben@decadent.org.uk>
Cc: "Matthew Carlson" <mcarlson@broadcom.com>,
	"Michael Chan" <mchan@broadcom.com>,
	"645308@bugs.debian.org" <645308@bugs.debian.org>,
	"Marc Haber" <mh+debian-bugs@zugschlus.de>,
	netdev <netdev@vger.kernel.org>
Subject: Re: Bug#645308: tg3 broken for NetXtreme 5714S in squeeze 6.0.3 installer
Date: Mon, 24 Oct 2011 14:24:09 -0700	[thread overview]
Message-ID: <20111024212409.GA29764@mcarlson.broadcom.com> (raw)
In-Reply-To: <1319199579.2918.42.camel@deadeye>

On Fri, Oct 21, 2011 at 05:19:39AM -0700, Ben Hutchings wrote:
> On Fri, 2011-10-21 at 11:08 +0200, Marc Haber wrote:
> > On Fri, Oct 21, 2011 at 11:00:46AM +0200, Marc Haber wrote:
> > > On Thu, Oct 20, 2011 at 05:28:34AM +0100, Ben Hutchings wrote:
> > > > I don't see any changes that would obviously change the way this device
> > > > is reconfigured during a down/up cycle.  There were some changes to
> > > > power management that should just let the PCI core do some work that the
> > > > driver used to, but it's possible that the result isn't quite the same.
> > > > I built a module with those reverted; source and binary attached.  Could
> > > > you test that?  I checked that d-i does include an insmod command.
> > > 
> > > The squeeze 6.0.3 installer with the shipped tg3.ko replaced with
> > > yours boots and networks just fine without any workaround and without
> > > manual interaction.
> > 
> > I was a bit fast on that. The interface now fails right in the middle
> > of installation and needs the modprobe -r, modprobe stunt to network
> > again.
> 
> Matt, Michael,
> 
> The tg3 driver has regressed for the 5714S since Linux 2.6.32.  Marc
> Haber found this in the backported version included in our stable
> update, but also confirmed it in Linux 3.0.
> 
> Bringing the interface down and then up again (which the installer does
> for some reason) can leave it unable to pass traffic (possibly after
> working for a few packets) until the module is reloaded.
> 
> I asked Marc to check whether reverting the power management changes
> (071697e2bcd8dff2af4d6fdd6525c2324f89553b,
> d237d9ecf06a00f0ebca657958cf2a1e92940796) made a difference, but it
> doesn't seem to.
> 
> There is more information in the bug log at
> <http://bugs.debian.org/645308>.

Where can I get the sources for this driver?  Commit
9e975cc291d80d5e4562d6bed15ec171e896d69b, entitled
"tg3: Fix io failures after chip reset" has been a common source of
problems.

  reply	other threads:[~2011-10-24 21:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20111017134430.GJ22096@torres.zugschlus.de>
     [not found] ` <20111017135137.GB4647@elie.hsd1.il.comcast.net>
     [not found]   ` <20111017135457.GL22096@torres.zugschlus.de>
     [not found]     ` <1318861800.3340.21.camel@deadeye>
     [not found]       ` <20111017144825.GM22096@torres.zugschlus.de>
     [not found]         ` <20111017160812.GL3366@decadent.org.uk>
     [not found]           ` <1318901100.3340.36.camel@deadeye>
     [not found]             ` <20111018142056.GF29261@torres.zugschlus.de>
     [not found]               ` <1319084914.23980.96.camel@deadeye>
     [not found]                 ` <20111021090046.GA13930@torres.zugschlus.de>
     [not found]                   ` <20111021090811.GA5993@torres.zugschlus.de>
2011-10-21 12:19                     ` Bug#645308: tg3 broken for NetXtreme 5714S in squeeze 6.0.3 installer Ben Hutchings
2011-10-24 21:24                       ` Matt Carlson [this message]
2011-10-24 23:47                         ` Ben Hutchings
2011-10-26  0:20                           ` Matt Carlson
2011-10-26  7:41                             ` Ben Hutchings
2011-11-18 19:54                               ` Matt Carlson
2011-11-19 18:45                                 ` Marc Haber
2011-11-19 19:37                                   ` Ben Hutchings
2011-11-19 20:13                                     ` Marc Haber

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20111024212409.GA29764@mcarlson.broadcom.com \
    --to=mcarlson@broadcom.com \
    --cc=645308@bugs.debian.org \
    --cc=ben@decadent.org.uk \
    --cc=mchan@broadcom.com \
    --cc=mh+debian-bugs@zugschlus.de \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.