------- Comment From kla...@br.ibm.com 2018-04-22 08:26 EDT------- (In reply to comment #121) > The kernel mentioned in #114 was a quick, rough attempt to force one instance > of free_work/del_work pending at a time. > > With that, the machine still seems to be up. > > root@boslcp3:~# uptime > 22:21:50 up 3:41, 2 users, load average: 77.72, 82.67, 81.90 > root@boslcp3:~# virsh list > Id Name State > ---------------------------------------------------- > 1 boslcp3g3 running > 2 boslcp3g4 running > 4 boslcp3g1 running > > And the logs still look clean!
Thanks for the excellent investigation here and on Bugzilla 167103, Dwip. Can you clarify the changes to the kernel mentioned in comment 114? How do they compare to the changes in Bz 165988 that we're considering reverting? -- 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
