public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Tanguy Ortolo <tanguy@ortolo.eu>
To: Realtek linux nic maintainers <nic_swsd@realtek.com>,
	Francois Romieu <romieu@fr.zoreil.com>
Cc: netdev@vger.kernel.org
Subject: Weird issue with r8169: shutdown on carrier comeback
Date: Mon, 2 Feb 2026 18:00:56 +0100	[thread overview]
Message-ID: <aYDYSHhaF1vQSxdW@ortolo.eu> (raw)

Hello,

I am experiencing a weird computer issue that is at least partly linked 
to the r8169 driver: the computer shuts down when the Ethernet cable is 
pulled off and plugged again. Or when the switch goes down and up again.

To be more specific, the computer is a [Trigkey Key-N100][1] running 
Debian Trixie. That computer has two Gigabit Ethernet controllers:
     $ lspci | grep Ethernet
     01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller (rev 15)
     02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller (rev 15)

[1]: https://devhome.corp.adobe.com/docs/default/component/ethos-flex/docs/devhome/prerequisites/

One of them is configured, and when I pull off its Ethernet cable and 
plug it again after a few seconds (or if I reboot the switch it is 
connected to), something simulates a power key press (log from 
systemd-logind: “Power key pressed short”). Even though I configured 
logind to ignore such events, one second after this, the computer shuts 
itself down brutally, as if experiencing a power loss.

After a few experiments, I determined that:
* it happens on both Ethernet interfaces of that computer;
* it happens only on _configured_ interfaces: in particular, it does not
   happen if I unplug the Ethernet cable, run `ip link set enp1s0 down`
   and plug the cable again;
* it does not happen with the proprietary driver r8168.

I am not really sure the r8169 driver is at fault here; it sounds more 
like a very weird hardware issue in specific conditions, which are met 
when using it. Anyway, I though you deserved to know, in case it could 
be useful. Please tell me if there is anything else I could do to 
further diagnose that issue.

Regards,

-- 
Tanguy Ortolo

             reply	other threads:[~2026-02-02 17:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-02 17:00 Tanguy Ortolo [this message]
2026-02-02 17:25 ` Weird issue with r8169: shutdown on carrier comeback Heiner Kallweit
2026-02-03 10:01   ` Tanguy Ortolo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aYDYSHhaF1vQSxdW@ortolo.eu \
    --to=tanguy@ortolo.eu \
    --cc=netdev@vger.kernel.org \
    --cc=nic_swsd@realtek.com \
    --cc=romieu@fr.zoreil.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox