That particular model is appearing a little too often.
That is even more strange.
So keeping the CPU active and busy prevents kernel panic?
I would seem it is somehow coupled with the specific iteration of the AMD Ryzen 7 PRO 6850U series. I have ThinkPad with 7840U - I don’t see these issues?
Has anyone of you tested Linux 6.11.0-rc4 - unstable?
$ mbn info linux611 -q
Branch : unstable
Name : linux611
Version : 6.11.0rc4-3
Repository : core
Build Date : Tue 20 Aug 2024 00:20:01
Packager : Manjaro Build Server <build@manjaro.org>
Branch : testing
Name : linux611
Version : 6.11.0rc3-2
Repository : core
Build Date : Tue 13 Aug 2024 10:33:18
Packager : Manjaro Build Server <build@manjaro.org>
Branch : stable
Name : linux611
Version : 6.11.0rc3-2
Repository : core
Build Date : Tue 13 Aug 2024 10:33:18
Packager : Manjaro Build Server <build@manjaro.org>
Well one has to speculate why the above line appears in your log - ecpcially considering that the list of supported ThinkPads → Thinkpad-acpi - ThinkWiki does not include P16s
Have you installed any ThinkPad specific packages from the repos?
Have you build any custom ThinkPad related sources?
Have you tried disabling the virtual extensions in the firmware?
If you do require the virtual extensions - at least try disabling as a test - and try to reproduce the issue.
Have you considered uninstalling VirtualBox, including the kernel modules (specifically vboxdrv)?
My reasoning is that the problem seems to be linked to VMs, so perhaps there’s some issue with VirtualBox, and in particular the kernel module, that’s causing a kernel panic when no VMs are loaded. I have no idea why that would be the case, but it seems worth checking.
There is no indication that your AMD cpu or system for that matter is the same as OP.
The kernel is the software that interacts with the system.
Kernel panic describes a situation where the kernel meets unexpected values or conditions - and don’t know how to handle them. This can be caused by a bug in the kernel or a driver or a failure in a hardware component.
Basically most hardware has their own CPU’s which is preconfigured with yet another type of kernel - that goes for disk devices, usb devices, cpus, gpus - and the list goes on.
Since kernel panic can have a broad range of causes and since it is stated that running a virtual machine stablilized the system
One could
boot a live ISO and test the system ram using memtest+
test with virtualization enabled and disabled
enable - disable virtual extension in the firmware
test the system with extensions enabled and disabled
I have two systems running AMD - I have never had random kernel panic - ever…