Bug#635341: eth0 unavailable after standby until reload of e1000e

2011-08-25 Thread Christian G. Warden
On Thu, Aug 25, 2011 at 09:47:01AM +0200, Diggory Hardy wrote: > Unfortunately I've still experienced this bug twice with the 3.0.0-1-amd64 > kernel, so the problem's still there. > > I presume it's a resume bug that needs to be filed against the e1000e module > upstream? fwiw, I haven't had this

Bug#635341: eth0 unavailable after standby until reload of e1000e

2011-08-25 Thread Diggory Hardy
Sure, then I'll wait until a debian package is available. I'm on holiday from this week end so it'll probably be at least a couple of weeks before I get to that (since I don't see a 3.1 RC package available yet). Cheers

Bug#635341: eth0 unavailable after standby until reload of e1000e

2011-08-25 Thread Jonathan Nieder
Diggory Hardy wrote: > Package version is: > linux-image-3.0.0-1-amd64 3.0.0-1 > > Presumably this tells you what version of e1000e is used? Yes, that's good enough. :) I was asking in order to tell if it was 3.0.0-1 or 3.0.0-2 (since both use the same linux-image-3.0.0-1-amd64 package nam

Bug#635341: eth0 unavailable after standby until reload of e1000e

2011-08-25 Thread Diggory Hardy
Package version is: linux-image-3.0.0-1-amd64 3.0.0-1 Presumably this tells you what version of e1000e is used? Thanks for the link, I'll have a look into reporting later. Diggory On 25 August 2011 10:51, Jonathan Nieder wrote: > reassign 635341 src:linux-2.6 2.6.39-2 > found 635341 linu

Bug#635341: eth0 unavailable after standby until reload of e1000e

2011-08-25 Thread Jonathan Nieder
reassign 635341 src:linux-2.6 2.6.39-2 found 635341 linux-2.6/3.0.0-1 quit Diggory Hardy wrote: > Unfortunately I've still experienced this bug twice with the 3.0.0-1-amd64 > kernel, so the problem's still there. Thanks for the update. What version of the package are you using? ("dpkg-query -W

Bug#635341: eth0 unavailable after standby until reload of e1000e

2011-08-25 Thread Diggory Hardy
Unfortunately I've still experienced this bug twice with the 3.0.0-1-amd64 kernel, so the problem's still there. I presume it's a resume bug that needs to be filed against the e1000e module upstream?

Bug#635341: eth0 unavailable after standby until reload of e1000e

2011-08-02 Thread Christian G. Warden
I'm also experiencing this problem with 2.6.39-2-amd64 on a ThinkPad T420. It doesn't happen every time I resume from suspend, but at least half of the time. Unloading e1000e and reloading it once sometimes doesn't fix it; I need to try repeatedly. Christian -- To UNSUBSCRIBE, email to debia

Bug#635341: eth0 unavailable after standby until reload of e1000e

2011-07-28 Thread Diggory Hardy
I'd give a rough estimate the malfunctioning-eth0 bug happens around half the time on resume from standby. Installing 3.0 kernel now for testing purposes.