[Bug 84681] New: No network after some S4 suspend/resume cycles
bugzilla-daemon at bugzilla.kernel.org
bugzilla-daemon at bugzilla.kernel.org
Tue Sep 16 13:00:20 PDT 2014
https://bugzilla.kernel.org/show_bug.cgi?id=84681
Bug ID: 84681
Summary: No network after some S4 suspend/resume cycles
Product: Drivers
Version: 2.5
Kernel Version: 3.17-rc4
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - Intel)
Assignee: intel-gfx-bugs at lists.freedesktop.org
Reporter: jens-bugzilla.kernel.org at spamfreemail.de
CC: intel-gfx-bugs at lists.freedesktop.org
Regression: No
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! :)
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the intel-gfx-bugs
mailing list