------- Comment From chetj...@in.ibm.com 2018-04-12 01:24 EDT------- (In reply to comment #18) > Can you see if the bug happens with and of these mainline kernels? We can > perform a kernel bisect if we can narrow down to the last good kernel > version and first bad one: > > v4.14 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14/ > v4.15-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc1/ > v4.15-rc4: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc4/ > v4.15 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15/ > > You don't have to test every kernel, just up until the kernel that first has > this bug. > > Thanks in advance!
We need to make progress in testing other firmware and guest issues. We will come back to this later. Meanwhile, the problem happened again today with the reboot and we tried to collect the vmcore using 'X', but it did not collect. Indira, pls add those details. -- 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 firstname.lastname@example.org https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs