virtual: 0.916 permissions: 0.908 user-level: 0.900 KVM: 0.882 risc-v: 0.880 device: 0.878 peripherals: 0.877 architecture: 0.871 VMM: 0.869 kernel: 0.868 vnc: 0.865 x86: 0.865 socket: 0.863 assembly: 0.856 network: 0.853 debug: 0.849 register: 0.849 files: 0.846 PID: 0.846 arm: 0.845 graphic: 0.840 performance: 0.838 TCG: 0.836 boot: 0.830 hypervisor: 0.825 semantic: 0.821 mistranslation: 0.795 i386: 0.758 ppc: 0.743 jammy qemu x86 int3: 0000 [#1] SMP NOPTI jammy:linux-lowlatency-hwe-6.8 6.8.0-44.44.1~22.04.1 qemu-x86 QEMU Standard PC (i440FX + PIIX, 1996) Recently (2024.08.05), I have been seeing this issue with ADT:systemd:upstream-1/2 test in which kernel panics/prints a stack. I have seen this with jammy:linux-lowlatency-hwe-6.8 and jammy:linux-ibm-6.8. Stack trace is different everytime because kernel receives an interrupt, drop what it is doing, and crash when handling the interrupt. I think this is an issue with qemu and not kernel. For jammy, we are using qemu 6.2 and there are some fixes related to x86 interrupt handling in 8.x (https://