Race conditions in places like this are exceedingly hard to write reliable tests for. It may take one, two boots; dozens, or thousands, or you may just get insanely lucky and whatever arbitrary # boots you do to try and reproduce it was still simply not enough. It's hard to have any level of confidence, in many cases.
There are acceptance tests, intergration test and actually many other types. I'm similarly not familiar with kernel dev. Have studies both operating systems and distributed systems aswell as CS. But the build checked all the right boxes.
Honestly I don't know! We've seen it appear with host kernel 6.2.15 (https://bugzilla.redhat.com/show_bug.cgi?id=2213346#c5) but I'm not aware of anyone either reproducing or not reproducing it with earlier host kernels. All your other config looks right.
I noticed it hangs in similar way when you insert msleep anywhere before smp_prepare_cpus in kernel_init_freeable. But I have no idea whether sleeping is valid here.
Thanks for pointing this out. Is it considered standard practice for websites to ignore unrecognized query parameters? Disclaimer: I'm not a front-end engineer; we put the site up in a bit of a hurry, using the framework I usually use for REST API's, where typically you want to error out if given unknown query strings.
Having JS variables inside JSX inside JS IIFE:s inside JSX inside JS feels bad to me. Current mainstream frontend development does not care about my feelings though.
