RE: [E1000-devel] e1000e suspend-to-disk reboots box with 3.11-rc3+
From: Allan, Bruce W
Date: Wed Jul 31 2013 - 17:13:18 EST
> -----Original Message-----
> From: Borislav Petkov [mailto:bp@xxxxxxxxx]
> Sent: Wednesday, July 31, 2013 1:41 PM
> To: e1000-devel@xxxxxxxxxxxxxxxxxxxxx
> Cc: netdev@xxxxxxxxxxxxxxx; linux-kernel@xxxxxxxxxxxxxxx
> Subject: [E1000-devel] e1000e suspend-to-disk reboots box with 3.11-rc3+
> I'm experiencing the strange observation that when I hibernate my x230
> with Linus HEAD from today + tip/master (3.11-rc3+), the box doesn't
> remain off but reboots immediately.
> Since I have a similar bug where an e1000e box reboots
> when "Wake on LAN from S4/S5" is enabled in the BIOS
> (https://bugzilla.novell.com/show_bug.cgi?id=812592) I decided to test
> with LAN cable removed.
> And yes, when the ethernet cable is not connected, the box hibernates
> and remains off. When I hibernate with the cable attached, the box
> doesn't remain off but reboots.
> The card is:
> [ 1.620772] e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k
> [ 1.622116] e1000e: Copyright(c) 1999 - 2013 Intel Corporation.
> [ 1.623687] e1000e 0000:00:19.0: setting latency timer to 64
> [ 1.625160] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to
> dynamic conservative mode
> [ 1.626640] e1000e 0000:00:19.0: irq 44 for MSI/MSI-X
> [ 1.884432] e1000e 0000:00:19.0 eth0: registered PHC clock
> [ 1.885925] e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1)
> [ 1.887466] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network
> [ 1.889089] e1000e 0000:00:19.0 eth0: MAC: 10, PHY: 11, PBA No: 1000FF-
> And of course, 3.10 is fine.
> Any ideas?
> I'll try to bisect it when I get a chance.
Off the top of my head, I cannot think of anything that has been added to the driver in
Linus' tree since 3.10 that would cause this change in behavior. There are a number of
changes that have been put into the out-of-tree driver which have not yet made it into
Linus' tree - would you be willing to try the latest out-of-tree driver from e1000.sf.net
to see if it resolves your issue? Of course, a bisect as you mention would also help.
Have you checked for a BIOS update from your system manufacturer?
Do you have Runtime Power Management enabled for this device?
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/