All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tanguy Ortolo <tanguy@ortolo.eu>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: Realtek linux nic maintainers <nic_swsd@realtek.com>,
	Francois Romieu <romieu@fr.zoreil.com>,
	netdev@vger.kernel.org
Subject: Re: Weird issue with r8169: shutdown on carrier comeback
Date: Tue, 3 Feb 2026 11:01:14 +0100	[thread overview]
Message-ID: <aYHHanMLATZ5kE50@ortolo.eu> (raw)
In-Reply-To: <602a08b9-134f-421e-bc2a-b89b0867b2e3@gmail.com>

Hello,

Thank you for the quick reply.

Heiner Kallweit, 2026-02-02 18:25+0100:
>Thanks for the report. Interesting issue .. The network driver (r8169) has no link to the input system.
>Therefore it's likely your network manager which is causing this behavior.

I doubt it, the network is simply managed by Debian's ifupdown. Nothing 
fancy like NetworkManager for instance. By the way, I tried after 
switching to systemd-networkd, and the issue remains.

(I also tried after enabling ifplugd, which deconfigures the interface 
when a carrier loss is detected, and that does avoid the problem, just 
like when I do the same manually: shutdown only happens when I re-plug 
the cable into an interface that is still configured.)

I would more likely suspect something weird in the motherboard itself. 
But this is indeed very hard to tell. I reported the issue to the 
manufacturer as well (Trigkey), but I am not sure they will reply. I do 
not see how the r8169 driver could be responsible for that issue, I 
think it merely creates conditions in which some hardware bug appears.

But since r8168 does not trigger that issue, I felt I should report it 
just in case it could be useful. Do not waste too much time on this. :-)

Regards,

-- 
Tanguy Ortolo

      reply	other threads:[~2026-02-03 10:01 UTC|newest]

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

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=aYHHanMLATZ5kE50@ortolo.eu \
    --to=tanguy@ortolo.eu \
    --cc=hkallweit1@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.