Message-ID: <4f40294f6e970c7c39c5eda9c98fe212005e4af4.camel@gmail.com>
Date: Wed, 19 Nov 2025 09:17:21 +1100
From: Jason Lethbridge <lethbridgejason@...il.com>
To: Heiner Kallweit <hkallweit1@...il.com>, nic_swsd@...ltek.com
Cc: netdev@...r.kernel.org
Subject: Re: Bug: Realtek 8127 disappears from PCI bus after shutdown

> ethtool -s <if-name> wol g
Running this command resolves the issue regardless of the Wake-on-LAN
setting in the UEFI is enabled or disabled. If the command is only ran
against one of the interfaces then that interface will appear on next
power on while the other won't.

On Tue, 2025-11-18 at 22:43 +0100, Heiner Kallweit wrote:
> On 11/18/2025 10:09 PM, Jason Lethbridge wrote:
> > 
> > > - How is it after a suspend-to-ram / resume cycle?
> > This machine is having trouble resuming from suspend-to-ram. I
> > doubt
> > that it's a problem relating to r8169 however since suspend-to-ram
> > doesn't work properly even with r8169 blacklisted.
> > 
> > > - Does enabling Wake-on-LAN work around the issue?
> > r8169 behaves the same regardless of if Wake-on-LAN is enable or
> > disabled in UEFI.
> > 
> Thanks for the feedback. Enabling WoL in UEFI isn't sufficient.
> It has to be enabled also on the chip:
> 
> ethtool -s <if-name> wol g
> 
> 
> > > - Issue also occurs with r8127 vendor driver?
> > The "10G Ethernet LINUX driver r8127 for kernel up to 6.15
> > 11.015.00"
> > from 'https://www.realtek.com/Download/List?cate_id=584' builds and
> > runs flawlessly on 6.17.8. The issue is not occurring when the NICs
> > are
> > driven by the r8127 module.
> > 
> > Drivers SHA-256:
> > ab21bf69368fb9de7f591b2e81cf1a815988bbf086ecbf41af7de9787b10594b 
> > r8127-11.015.00.tar.bz2
> > 
> > On Tue, 2025-11-18 at 20:49 +0100, Heiner Kallweit wrote:
> > > On 11/18/2025 6:07 PM, Jason Lethbridge wrote:
> > > > Hi all,
> > > > 
> > > > I’m reporting a reproducible issue with the r8169 driver on
> > > > kernel
> > > > 6.17.8.
> > > > 
> > > > I recently got a Minisform MS-S1 which has two RTL8127 NICs
> > > > built
> > > > in.
> > > > The r8169 driver works perfectly well with these on kernel
> > > > 6.17.8
> > > > until
> > > > the device is powered off.
> > > > 
> > > > If the device has not been disconnected from wall power then
> > > > the
> > > > next
> > > > time it's turned on both NICs appear to stay powered down.
> > > > There's
> > > > no
> > > > LED illuminated on the NIC or the switch they're connected to
> > > > nor
> > > > are
> > > > they listed by lspci. The only way to recover the NICs from
> > > > this
> > > > state
> > > > is to disconnect the power then plug it back in.
> > > > 
> > > - How is it after a suspend-to-ram / resume cycle?
> > > - Does enabling Wake-on-LAN work around the issue?
> > > - Issue also occurs with r8127 vendor driver?
> > > 
> > > > - The bug occurs after graceful shutdown
> > > > - The bug occurs after holding the power button to force off
> > > > - The bug occurs even if `modprobe -r r8169` is run before
> > > > shutdown
> > > > - The bug does NOT occur when Linux is rebooting the machine
> > > > - The bug does NOT occur when the r8169 module is blacklisted
> > > > - The bug is indifferent to either NIC being connected or not
> > > > - The bug is indifferent to CONFIG_R8169 being in-built or a
> > > > module
> > > > - The bug is indifferent to CONFIG_R8169_LEDS being set on or
> > > > off
> > > > 
> > > > Attachments include `dmesg`, `lspci -vvv`, and
> > > > `/proc/config.gz`
> > > > from
> > > > the system exhibiting the bug.
> > > > 
> > > > I'll be happy to try any patches if that helps.
> > > > 
> > > > Thanks
> > > > -Jason

Powered by blists - more mailing lists