** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Cosmic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1809847
Title:
Ethernet[10ec:8136] doesn't work after S3 with kernel 4.15.0.43.64
Status in HWE Next:
New
Status in OEM Priority Project:
Confirmed
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
Fix Committed
Bug description:
[Impact]
The Ethernet works after S3 with kernel 4.15.0-33.36, and fails with kernel
4.15.0.43.64.
There is no interrupt while plug/unplug Ethernet cable after S3, so it looks
like a regression after 4.15.0-33.36.
[Fix]
Check changelog and found there are 2 commits introduced from 4.15.0-35.38
might be suspicious
* r8169 no internet after suspending (LP: #1779817)
- r8169: don't use MSI-X on RTL8168g
- r8169: don't use MSI-X on RTL8106e
And check the upstream log and found the 2 MSI-X commits had been all
reverted, since below commit claims it fixes the MSI-X interrupt issue which is
already in Bionic kernel.
083874549fdf PCI: Reprogram bridge prefetch registers on resume
So, I reverted the 2 MSI-X commits and found the Ethernet works again after
S3.
[Regression Potential]
Low, the 2 disable MSI-X commits are workarounds, and now we have proper way
to fix the issue, so it should be fine to revert them.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1809847/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
