From: Bert Karwatzki <spasswolf@web.de>
To: Joel Fernandes <joelagnelf@nvidia.com>
Cc: linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
linux-rt-devel@lists.linux.dev, ankur.a.arora@oracle.com,
bobo.shaobowang@huawei.com, boqun.feng@gmail.com,
frederic@kernel.org, joel@joelfernandes.org,
neeraj.upadhyay@kernel.org, paulmck@kernel.org,
rcu@vger.kernel.org, urezki@gmail.com,
wangxiongfeng2@huawei.com, xiexiuqi@huawei.com,
xiqi2@huawei.com, spasswolf@web.de
Subject: Re: commit 3284e4adca9b causes hang on boot with CONFIG_PREEMPT_RT=y
Date: Sat, 12 Jul 2025 01:27:37 +0200 [thread overview]
Message-ID: <21da96d766d92735e5fe022f54d686df8bdfc32d.camel@web.de> (raw)
In-Reply-To: <862fa11d-0f9a-4193-91d1-ea930d2d334f@nvidia.com>
Am Freitag, dem 11.07.2025 um 19:06 -0400 schrieb Joel Fernandes:
>
> On 7/11/2025 7:00 PM, Bert Karwatzki wrote:
> > When booting linux next-20250711 (with CONFIG_PREEMPT_RT=y) on my MSI Alpha 15
> > Laptop running debian sid amd64 the boot process hangs with the last
> > messages displayed on screen being:
> >
> > fbcon: amdgpudrmfb (fb0) is primary device
> > Console: switching to colour frame buffer device
> > amdgpu: 0000:08:00.0: [drm]fb0: admgpudrmfb frame buffer device
> >
> > after some time (about 60s) this error messages appears (hand copied
> > from screen, not entirely accurate)
> >
> > rcu_preempt self detected stall
> >
> > with call trace
> > run_irq_workd
> > smpboot_thread_fn
> > kthread
> > ? kthreads_online_cpu
> > ? kthreads_online_cpu
> > ret_from_fork
> > ? kthreads_online_cpu
> > ret_from_fork
> >
> > This only occurs when compiling with CONFIG_PREEMPT_RT=y.
> > I bisected this and found the first bad commit to be
> >
> > 3284e4adca9b ("rcu: Fix rcu_read_unlock() deadloop due to IRQ work")
>
> This commit is still using old code which was fixed in the last day.
>
> Here is the new commit:
> https://web.git.kernel.org/pub/scm/linux/kernel/git/rcu/linux.git/commit/?h=next&id=2e154d164418e1eaadbf5dc58cbf19e7be8fdc67
>
> Thanks!
>
> - Joel
I already found the new commit, it works!
Bert Karwatzki
prev parent reply other threads:[~2025-07-11 23:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-11 23:00 commit 3284e4adca9b causes hang on boot with CONFIG_PREEMPT_RT=y Bert Karwatzki
2025-07-11 23:06 ` Joel Fernandes
2025-07-11 23:27 ` Bert Karwatzki [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=21da96d766d92735e5fe022f54d686df8bdfc32d.camel@web.de \
--to=spasswolf@web.de \
--cc=ankur.a.arora@oracle.com \
--cc=bobo.shaobowang@huawei.com \
--cc=boqun.feng@gmail.com \
--cc=frederic@kernel.org \
--cc=joel@joelfernandes.org \
--cc=joelagnelf@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=neeraj.upadhyay@kernel.org \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=urezki@gmail.com \
--cc=wangxiongfeng2@huawei.com \
--cc=xiexiuqi@huawei.com \
--cc=xiqi2@huawei.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).