Hi jlmera, Thanks for your bug report!
The fact that this error is a one-off, the corruption occurs in a heavily exercised and well-tested part of the kernel, and the system's i9 14900K CPU is known for having stability issues with initial firmware and microcode revisions, it seems very possible that the issue you ran into is a hardware one. Note that if the CPU ran long enough in the wrong conditions caused by early firmware/microcode revisions, it is possible the CPU silicon is permanently degraded. I would suggest checking if your motherboard has newer firmware available, and that your CPU is running the latest microcode revision available for it. If this doesn't resolve your issue, you can try the following: * Add the `oops=panic` kernel boot parameter to immediately panic the system and reboot when this issue occurs. This can help avoid the hang by rebooting as soon as the issue occurs. * With `oops=panic` still enabled, also enable crash dumps using the following instructions: https://ubuntu.com/server/docs/how- to/software/kernel-crash-dump/. Collecting a crash dump will help us investigate the issue further. * Try to recreate the issue and identify steps that allow you to reliably reproduce it. ** Also affects: linux (Ubuntu Questing) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu Questing) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2157705 Title: linux-hwe-6.17 6.17.0-35: kernel page-fault Oops in zap_present_ptes during exit_mmap; dying task leaves page-table lock + RCU read-side held -> RCU stalls + kcompactd soft lockup -> full system hang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2157705/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
