Comment 2 for bug 2032176
Revision history for this message
| Stefan Bader (smb) wrote Re: Crashing with CPU soft lock on HWE kernel 5.19.0-46.47-22.04.1 | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
f33e652
(Get the code!)
The problem is the missing start of the issue. What is there indicates that the VM ran into a page fault situation and is stuck in a lock. From other reports the console display might be part of a soft cpu lockup detected message. This is often the result of a previous crash (which leaves locks in locked state). Would it be possible to reset a stuck instance and retrieve the rotated journal?
The other problem is that the virtualization stack cannot really be deducted from the given info. There is at least one level of VM. The instance in openstack. Question: is the juju "machine" a secondary VM on the openstack instance? The available trace suggests that the lockup occurred on an AMD CPU. This is relevant for VMs as Intel and AMD use different virt. extensions (SVM vs VMX).
Other note on 5.19: the HWE kernel rolled to 6.2 with 22.04.3. I know this could result in other issues but maybe it is one possible option for the current situation.