From: Joel Fernandes <joelagnelf@nvidia•com>
To: Bert Karwatzki <spasswolf@web•de>
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
Subject: Re: commit 3284e4adca9b causes hang on boot with CONFIG_PREEMPT_RT=y
Date: Fri, 11 Jul 2025 19:06:08 -0400 [thread overview]
Message-ID: <862fa11d-0f9a-4193-91d1-ea930d2d334f@nvidia.com> (raw)
In-Reply-To: <20250711230042.3468-1-spasswolf@web.de>
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
next prev parent reply other threads:[~2025-07-11 23:06 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 [this message]
2025-07-11 23:27 ` Bert Karwatzki
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=862fa11d-0f9a-4193-91d1-ea930d2d334f@nvidia.com \
--to=joelagnelf@nvidia$(echo .)com \
--cc=ankur.a.arora@oracle$(echo .)com \
--cc=bobo.shaobowang@huawei$(echo .)com \
--cc=boqun.feng@gmail$(echo .)com \
--cc=frederic@kernel$(echo .)org \
--cc=joel@joelfernandes$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-rt-devel@lists$(echo .)linux.dev \
--cc=neeraj.upadhyay@kernel$(echo .)org \
--cc=paulmck@kernel$(echo .)org \
--cc=rcu@vger$(echo .)kernel.org \
--cc=spasswolf@web$(echo .)de \
--cc=urezki@gmail$(echo .)com \
--cc=wangxiongfeng2@huawei$(echo .)com \
--cc=xiexiuqi@huawei$(echo .)com \
--cc=xiqi2@huawei$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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