From: Sean Anderson <sean.anderson@linux.dev>
To: Mike Galbraith <efault@gmx.de>,
Robert Hancock <robert.hancock@calian.com>
Cc: Breno Leitao <leitao@debian.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: netpoll: raspberrypi [4 5] driver locking woes
Date: Thu, 28 Aug 2025 10:57:42 -0400 [thread overview]
Message-ID: <cbc6389e-069e-4f59-8544-fa59678e401b@linux.dev> (raw)
In-Reply-To: <f4fa3fcc637ffb6531982a90dbd9c27114e93036.camel@gmx.de>
Hi Mike,
On 8/27/25 12:02, Mike Galbraith wrote:
> Unexpected addendum to done deal datapoint, so off list.
>
> On Tue, 2025-08-26 at 11:49 +0200, Mike Galbraith wrote:
>>
>> The pi5 gripe fix is equally trivial, but submitting that is pointless
>> given there's something else amiss in fingered commit. This is all of
>> the crash info that escapes the box w/wo gripes silenced.
>>
>> [ 51.688868] sysrq: Trigger a crash
>> [ 51.688892] Kernel panic - not syncing: sysrq triggered crash
>> [ 51.698066] CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Not tainted 6.17.0-rc2-v8-lockdep #533 PREEMPTLAZY
>> [ 51.707234] Hardware name: Raspberry Pi 5 Model B Rev 1.0 (DT)
>> [ 51.713085] Call trace:
>> [ 51.715532] show_stack+0x20/0x38 (C)
>> [ 51.719206] dump_stack_lvl+0x38/0xd0
>> [ 51.722878] dump_stack+0x18/0x28
>>
>> That aspect is a punt and run atm (time.. and dash of laziness:).
>
> Plan was to end datapoint thread, but after booting pi5's 6.12 kernel,
> for some reason I fired up netconsole.. and box promptly exhibited the
> netpoll locking bug warning, indicating presence of 138badbc21a0.
> Instead of saying to self "nope, just walk away", I poked SysRq-C.. and
> the bloody damn monitoring box received a 100% complete death rattle.
> Well bugger.
Did you get a backtrace for this?
And to be clear, the steps to reproduce this are to boot a kernel with
lockdep enabled with netconsole on macb and then hit sysrq?
> Two trees contain locking buglet introducing 138badbc21a0, 6.12.41 and
> 6.17.0, but only the later reproduces the above mess. A quick stare at
> git diff inspired checking e6a532185daa, and sure enough reverting only
> it reproduced a functional netconsole, modulo warnings, ie the mess
> above manifests only with BOTH resident. Either revert 138badbc21a0,
> or revert e6a532185daa and fix the 138badbc21a0 locking buglet, and the
> result is the same, a perfectly functional warning free netconsole.
next parent reply other threads:[~2025-08-28 14:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4698029bbe7d7a33edd905a027e3a183ac51ad8a.camel@gmx.de>
[not found] ` <e32a52852025d522f44d9d6ccc88c716ff432f8f.camel@gmx.de>
[not found] ` <f4fa3fcc637ffb6531982a90dbd9c27114e93036.camel@gmx.de>
2025-08-28 14:57 ` Sean Anderson [this message]
2025-08-28 17:26 ` netpoll: raspberrypi [4 5] driver locking woes Mike Galbraith
2025-08-28 18:56 ` Sean Anderson
2025-08-29 2:55 ` Mike Galbraith
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=cbc6389e-069e-4f59-8544-fa59678e401b@linux.dev \
--to=sean.anderson@linux.dev \
--cc=efault@gmx.de \
--cc=leitao@debian.org \
--cc=netdev@vger.kernel.org \
--cc=robert.hancock@calian.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;
as well as URLs for NNTP newsgroup(s).