netdev - Re: Tulip 21142 panic on physical link disconnect

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: <6a079cd0233b33c6faf6af6a1da9661f@wizardsworks.org>
Date: Tue, 17 Jun 2025 11:19:39 -0700
From: Greg Chandler <chandleg@...ardsworks.org>
To: Florian Fainelli <f.fainelli@...il.com>
Cc: stable@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: Tulip 21142 panic on physical link disconnect

Hmm...  I'm wondering if that means it's an alpha-only issue then, which 
would make this a much larger headache than it already is.
Also thank you for checking, I appreciate you taking the time.

I assume the those interfaces actually work right? (simple ping over 
that interface would be enough)  I posted in a subsequent message that 
mine do not appear to at all.

My next step is to build that driver as a module, and see if it changes 
anything (I'm doubting it will).
Then after that go dig up a different adapter, and see if it's the 
network stack or the driver.

I've been hard pressed over the last week to get a lot of diagnosing 
time.

On 2025/06/16 12:01, Florian Fainelli wrote:
> On 6/10/25 11:53, Greg Chandler wrote:
>> 
>> 
>> I decided to test this again before I got sidetracked on my bigger 
>> issue.
>> The kernel I repored this on was 6.12.12 on alpha, this is also that 
>> same version, but with a make distclean, and just about every single 
>> debug option turned on.
>> 
>> I left the last line of the kernel boot in this output as well, 
>> showing "link beat good"
>> 
>> I pulled the plug and it happened again immediately.
>> I waited 10 sec, and plugged it back in, and I do not get a "link up" 
>> type message that I would expect to see.
> 
> I was not able to reproduce this on my Cobalt Qube2 with the link being 
> UP and then pulling the cable unfortunately, I could try other things 
> if you want me to.