Perhaps the next step is trying to figure out which mitigation exactly causes it to fail. Then kernel peeps should have a fighting chance of tracking this down
The mitigations work by making sure to clear everything they can when the CPU switches contexts. This includes clearing loaded local CPU cache, clearing the branch prediction table, clearing all speculative execution entries. The mitigations likely avoid a crash by clearing something that should be cleared between context switches in all cases. As in the mitigations likely accidentally fix this. Which is a good clue. It'd be nice if the mitigations were more fine grained than all or nothing so we could turn on the mitigations one by one but the microcode is not open so we can't do this :(.
[1]: https://www.youtube.com/live/1UnoBfw6soI?si=R8nJ1FxdE4zBuO0i...
https://www.youtube.com/live/1UnoBfw6soI
Pretty shocking to see (supposedly) non-malicious code work / not-work depending on a security mitigation setting.
Curious to see where this goes as to whether it's a kernel bug and nobody is paying attention to mitigations=off now or the unlikely outcome that it's an actual hardware bug where mitigation work around it and nobody has noticed.