------- Comment From dougm...@us.ibm.com 2018-04-21 08:45 EDT------- The latest logs show a panic in process_one_work() on CPU 145, some sort of NULL pointer fault, followed by 2 CPUs (22, 125) getting a "Bad interrupt in KVM entry/exit code, sig: 6" panic (possibly in response to the panic IPI). Those 2 CPUs timeout and the KDUMP kexec starts.
The KDUMP then gets the same process_one_work() panic, this time on CPU 1, followed by Hard LOCKUP detected on CPUs 0 and 1. rcu_sched then starts detecting the stalled CPU(s), only trying to dump CPU 1. The problem seems to keep changing. Originally it was a panic on a very strange address in kmem_cache_alloc_node() from socket code. Later we see a NULL pointer issue in pool_mayday_timeout() from KVM. Now we are seeing a panic in process_one_work() from a kworker thread (unknown workqueue). If these different panics all have the same cause, it would seem to be something like memory corruption. Not being able to get a clean dump is going to be a problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762844 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1762844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
