netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Chandler <chandleg@wizardsworks.org>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: stable@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: Tulip 21142 panic on physical link disconnect
Date: Tue, 17 Jun 2025 11:19:39 -0700	[thread overview]
Message-ID: <6a079cd0233b33c6faf6af6a1da9661f@wizardsworks.org> (raw)
In-Reply-To: <fba6a52c-bedf-4d06-814f-eb78257e4cb3@gmail.com>


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.

  reply	other threads:[~2025-06-17 18:18 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-09 22:43 Tulip 21142 panic on physical link disconnect Greg Chandler
2025-06-10 16:27 ` Florian Fainelli
2025-06-10 18:33   ` Greg Chandler
2025-06-10 18:53   ` Greg Chandler
2025-06-16 19:01     ` Florian Fainelli
2025-06-17 18:19       ` Greg Chandler [this message]
2025-06-17 18:22         ` Florian Fainelli
2025-06-18 20:59           ` Greg Chandler
2025-06-18 22:51             ` Greg Chandler
2025-06-19 18:57               ` Greg Chandler
2025-06-19 19:36                 ` Maciej W. Rozycki
2025-06-19 19:46                   ` Florian Fainelli
2025-06-19 21:53                     ` Maciej W. Rozycki
2025-06-19 22:56                       ` Greg Chandler
2025-06-19 23:32                         ` Greg Chandler
2025-06-20  0:57                         ` Maciej W. Rozycki
2025-06-24 23:10                           ` Greg Chandler
2025-06-24 23:18                             ` Greg Chandler
2025-06-26 17:40                               ` Greg Chandler

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=6a079cd0233b33c6faf6af6a1da9661f@wizardsworks.org \
    --to=chandleg@wizardsworks.org \
    --cc=f.fainelli@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).