netdev - Re: Bug: Realtek 8127 disappears from PCI bus after shutdown

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <3a8e5e57-6a64-4245-ab92-87cb748926b5@gmail.com>
Date: Tue, 18 Nov 2025 20:49:49 +0100
From: Heiner Kallweit <hkallweit1@...il.com>
To: Jason Lethbridge <lethbridgejason@...il.com>, nic_swsd@...ltek.com
Cc: netdev@...r.kernel.org
Subject: Re: Bug: Realtek 8127 disappears from PCI bus after shutdown

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