Example QR code kernel panic screen
Requirement
MassOS experimental-20250830 and above.
May not work in VMs, as VM software can halt execution of, or shut off, the VM entirely after the kernel panic "disables" the CPU.
Some QR code scanners may be unable to read the v40 QR code format - try a different (more modern) program if this is the case. For the example image above, open it in a new window and zoom so the reader can pick it up more clearly.
Manually triggering a kernel panic
WARNING: This will immediately crash the kernel, and may cause data loss / filesystem corruption. Do not do it on production systems:
echo 1 | sudo tee /proc/sys/kernel/sysrq
echo c | sudo tee /proc/sysrq-trigger
Restoring old behaviour (kmsg)
Use the following kernel command-line parameter to restore the old behaviour of printing the kernel stack trace to the console instead of displaying the new QR code panic screen:
Example QR code kernel panic screen
Requirement
MassOS experimental-20250830 and above.
May not work in VMs, as VM software can halt execution of, or shut off, the VM entirely after the kernel panic "disables" the CPU.
Some QR code scanners may be unable to read the v40 QR code format - try a different (more modern) program if this is the case. For the example image above, open it in a new window and zoom so the reader can pick it up more clearly.
Manually triggering a kernel panic
WARNING: This will immediately crash the kernel, and may cause data loss / filesystem corruption. Do not do it on production systems:
Restoring old behaviour (kmsg)
Use the following kernel command-line parameter to restore the old behaviour of printing the kernel stack trace to the console instead of displaying the new QR code panic screen: