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>. Ben. -- Ben Hutchings Unix is many things to many people, but it's never been everything to anybody.
Attachment:
signature.asc
Description: This is a digitally signed message part