From: Matt Fleming <matt@readmodwrite.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: Tejun Heo <tj@kernel.org>, Andrea Righi <arighi@nvidia.com>,
sched-ext@lists.linux.dev, linux-kernel@vger.kernel.org,
kernel-team@cloudflare.com
Subject: Re: sched_ext/lavd hard lockup in old call_rcu_tasks_generic needadjust path
Date: Thu, 11 Jun 2026 14:02:58 +0100 [thread overview]
Message-ID: <aiqxpzgl2YVVSARw@matt-Precision-5490> (raw)
In-Reply-To: <2179fc11-3bd5-4d2e-9ad8-609e3356ec09@paulmck-laptop>
On Tue, Jun 09, 2026 at 04:23:23AM -0700, Paul E. McKenney wrote:
>
> Does commenting out the 'call_rcu_tasks_generic+547' printk() avoid the
> issue? If so, that printk() might be deferred or some such.
>
> "But if you cannot trust printk(), what *can* you trust?" ;-)
I tried this and it still crashes so apparently not! I'll keep digging
to find the real cause (it's somewhat cumbersome to reproduce this hard
lockup).
next prev parent reply other threads:[~2026-06-11 13:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 10:47 sched_ext/lavd hard lockup in old call_rcu_tasks_generic needadjust path Matt Fleming
2026-06-09 11:23 ` Paul E. McKenney
2026-06-11 13:02 ` Matt Fleming [this message]
2026-06-11 13:45 ` Paul E. McKenney
2026-06-12 10:55 ` Matt Fleming
2026-06-12 14:00 ` Paul E. McKenney
2026-06-16 10:56 ` Matt Fleming
2026-06-17 3:24 ` Paul E. McKenney
2026-06-18 6:56 ` Matt Fleming
2026-06-18 15:55 ` Paul E. McKenney
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=aiqxpzgl2YVVSARw@matt-Precision-5490 \
--to=matt@readmodwrite.com \
--cc=arighi@nvidia.com \
--cc=kernel-team@cloudflare.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=sched-ext@lists.linux.dev \
--cc=tj@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