APPLIED[D]: [SRU] [Unstable/OEM-B] [PATCH 0/2] r8169 doesn't get woken up by ethernet cable plugging, no PME generated

Seth Forshee seth.forshee at canonical.com
Wed Mar 20 19:45:07 UTC 2019


On Tue, Feb 26, 2019 at 04:56:55PM +0800, Kai-Heng Feng wrote:
> BugLink: https://bugs.launchpad.net/bugs/1817676
> 
> [Impact]
> Once r8169 (Realtek ethernet) and its root port enter to D3, plugging
> network cable doesn't wake r8169 up.
> 
> [Fix]
> Revert "PCI/PME: Implement runtime PM callbacks".
> Quote the original commit message:
> "
> The commit tried to prevent root port waking up from D3cold immediately but
> looks like disabing root port PME interrupt is not the right way to fix
> that issue so revert it now.  The patch following proposes an alternative
> solution to that issue.
> "
> 
> [Test]
> After applying the fix, plugging the ethernet cable can generate PME IRQ
> correctly, hence waking up r8169.
> 
> [Regression Potential]
> Medium. The commits are relative new, rely on some PCI detail that I am
> not familiar with (PCI spec isn't publicly available).
> Fortunately we only need this fix for Unstable/OEM-B, so it won't hit
> most users if any regression happens.

Applied patch 2 to disco/master-next. Patch 1 was already applied via
upstream stable updates. Since this patch is now upstream I modified the
commit message to remove linux-next from the "cherry picked from ..."
line. Thanks!



More information about the kernel-team mailing list