On Thu, 2026-06-18 at 01:11 +0800, Wen Yang wrote: > Thank you for your feedback. > I am using a WSL dev environment with 12 cores and 16GB. The config > of the tested kernel code is as follows:
Uhm that's a strange one, I cannot get a machine like that.. The closest is a 16 CPUs where I can limit the resources in vng. > And then, using vng to build and run kselftests (since kunit is > already > built-in) can reproduce this issue: > > $ vng --build > > $ vng -v --run arch/x86/boot/bzImage --user root -- > tools/testing/selftests/verification/verificationtest-ktap Well whenever I pass some argument to vng (instead of just vng -v that brings up an interactive shell), I see an unrelated lockdep splat in timekeeping_init(), but all clear when the KUnit runs.. I'm going to try and understand better what's going on, I don't think I can reproduce it easily. Thanks, Gabriele
