Bug 198973 - [Regression] r8169 RTL8101/2/6E not resumed after waiting mode (suspend)
Summary: [Regression] r8169 RTL8101/2/6E not resumed after waiting mode (suspend)
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: network-wireless (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: drivers_network-wireless@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-03-02 11:36 UTC by Mikhail Novosyolov
Modified: 2019-01-17 03:22 UTC (History)
6 users (show)

See Also:
Kernel Version: 4.15.3
Tree: Mainline
Regression: No


Attachments

Description Mikhail Novosyolov 2018-03-02 11:36:02 UTC
Notebook Lenovo Ideapad 100-14IBY 80MH
RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller, pci:10ec-8136-17aa-3830

1) suspend (waiting mode)
2) Wakeup
3) Ethernet controller is not active,
"rmmod r8169 && modprobe r8169" (reloading the driver) makes it work again.
There is no such bug with kernel 4.14, so it must be a regression.

Full hardware information, including dmesg after resuming and "rmmod r8169 && modprobe r8169", is here: https://linux-hardware.org/index.php?probe=250553ee30

I am not the owner of this hardware, the original user's bug report is here: https://vk.com/wall-33847957_238072
Comment 1 Mikhail Novosyolov 2018-04-29 08:44:06 UTC
The problem is active on 4.16
Comment 2 kiwwi 2018-04-29 23:11:56 UTC
I got the same problem on my Dell Vostro 5468 notebook. Driver r8169 was working on the kernel 4.14 but it's not working since then.
Comment 3 Heiner Kallweit 2018-05-14 08:37:48 UTC
Most likely same (resolved) issue as https://bugzilla.kernel.org/show_bug.cgi?id=199549 because RTL8168h/RTL8107e have identical chip XID.
Comment 4 Tony Morehen 2018-05-25 12:09:53 UTC
Same issue, resolved with a kernel upgrade to 4.17 rc5

laptop hp Pavilion G7
RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller, pci:10ec:8136
Manjaro 
kernel 4.16-8
Comment 5 Ben Wolsieffer 2018-07-20 01:10:35 UTC
I can confirm that this is resolved. I am running 4.17.3.

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