Bug 84681 - No network after some S4 suspend/resume cycles
Summary: No network after some S4 suspend/resume cycles
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: Network (show other bugs)
Hardware: x86-64 Linux
: P1 normal
Assignee: drivers_network@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-16 20:00 UTC by Jens
Modified: 2016-03-19 17:20 UTC (History)
3 users (show)

See Also:
Kernel Version: 3.18-0rc6
Subsystem:
Regression: No
Bisected commit-id:


Attachments

Description Jens 2014-09-16 20:00:20 UTC
This is an addendum to Bug #59321 which got fixed.
Same hardware (Haswell step 2, i4570, MSI-7817 B85m mainboard.

Here's the challenge:
Occasionally (about every fifth time) when I do S4 suspend and resume cycle, after resuming I have no network, meaning the interface is not coming up again. 

This is the dmesg of a SUCCESSFUL resume with networking:

...
[  335.912525] PM: restore of devices complete after 764.543 msecs
[  335.912632] PM: Image restored successfully.
[  335.912644] PM: Basic memory bitmaps freed
[  335.912645] Restarting tasks ... 
[  335.912708] r8169 0000:02:00.0: no hotplug settings from platform
[  335.914229] done.
[  335.914233] video LNXVIDEO:00: Restoring backlight state
[  336.112423] r8169 0000:02:00.0 eth1: link down
[  336.112457] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[  336.112479] r8169 0000:02:00.0 eth1: link down
[  338.889059] r8169 0000:02:00.0 eth1: link up
[  338.889064] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
...

This is the dmesg of a FAILED resume, without networking:

...
[ 1083.025140] PM: restore of devices complete after 764.906 msecs
[ 1083.025263] PM: Image restored successfully.
[ 1083.025275] PM: Basic memory bitmaps freed
[ 1083.025277] Restarting tasks ... 
[ 1083.025350] r8169 0000:02:00.0: no hotplug settings from platform
[ 1083.032115] done.
[ 1083.032120] video LNXVIDEO:00: Restoring backlight state
...

If I do S4 again it usually works again.

What can I do to get this fixed? 
Thank you! :)
Comment 1 Jens 2014-11-28 09:39:34 UTC
Any news on this bug? It still happens with 3.18.0rc6 (a834a782adf3ab4b508cd80e9082960263bcc4ed), see also https://bugs.freedesktop.org/show_bug.cgi?id=82864.

Thank you!
Comment 2 Jens 2015-08-12 18:37:53 UTC
This still happens with 4.2 kernels, even after updating the BIOS to 10.9 and resetting all BIOS settings to default. How can I help debug this problem? It basically prevents us from using S4 suspend at all, since without networking, the computer is not really usable.

Thanks!

Note You need to log in before you can comment on or make changes to this bug.