------- Comment From [email protected] 2018-05-02 16:32 EDT------- I think next steps here are:
1) apply all the known firmware workarounds (GH 1158) 2) Bring up system with Doug's recommendations for log verbosity (comment 211 and 215). Also capture the console output to a separate file if possible. 3) re-start the test using this same kernel, but with no stress on the host: proceed to restart the 3 guests with stress, and have a 4th guest migrating between boslcp3 and 4. ------- Comment From [email protected] 2018-05-02 16:36 EDT------- (In reply to comment #218) > I think next steps here are: > > 1) apply all the known firmware workarounds (GH 1158) > 2) Bring up system with Doug's recommendations for log verbosity (comment > 211 and 215). Also capture the console output to a separate file if possible. > 3) re-start the test using this same kernel, but with no stress on the host: > proceed to restart the 3 guests with stress, and have a 4th guest migrating > between boslcp3 and 4. Klaus, let's hold off on making more changes right now. I'd like to let things run as-is a little longer. ** Tags removed: bugnameltc-166588 kernel-key severity-critical triage-g -- 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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
