Le 17/02/2026 à 10:10 PM, 'Mark Brown' via KUnit Development a écrit :
Hi,
When running KUnit via qemu on current mailine I'm seeing random
lockups, frequently but not always reporting an RCU stall.
Unfortunately these don't seem to happen in a consistent place which
makes it hard to figure out exactly what's going on, they started in
-next at some point shortly before or early in the merge window but I've
never managed to drill down and investigate them. I don't imagine
they're due to KUnit specifically, though it seems likely some test is
triggering them. Has anyone else seen this, or do you have any leads?
Hmm… I haven't seen this yet on x86_64, but looking at arm64 and 32-bit
i386, I do see a sporadic panic, often with rcu in the stacktrace. Seems
to happen more often when the KUnit test kthread is starting/stopping
(particularly, at least on i386, if it's due to a trapped fault).
I've not been able to reproduce it after reverting the kthread affinity
series (git revert -m1 d16738a4e79e55b2c3c9ff4fb7b74a4a24723515), but
that could just be due to luck. It's flaky enough that my attempt at
bisection kept pointing at documentation patches.
Frederic, any idea if the 7.0 kthread updates could be causing these? My
most reliable repro command thus far is:
./tools/testing/kunit/kunit.py run --arch arm64 --make_options LLVM=1
— David
