If the kernel.log came from the same instance as the cpu info, this happened on an AMD CPU instance. Are there any Intel CPU hosts available in that openstack domain and if yes would it be possible to let the same 5.15.0-83-generic be used on that for a juju runner?
If that does not crash we could greatly limit the scope to search for changes to SVM. Otherwise it would be the wider area of generic memory management.
If the kernel.log came from the same instance as the cpu info, this happened on an AMD CPU instance. Are there any Intel CPU hosts available in that openstack domain and if yes would it be possible to let the same 5.15.0-83-generic be used on that for a juju runner?
If that does not crash we could greatly limit the scope to search for changes to SVM. Otherwise it would be the wider area of generic memory management.