(In reply to comment #80) > Hello Canonical, > > There are two problems here > > 1. Hang when CPUs don't respond to IPI. This can be resolved by setting a > non-zero panic timeout. > That fix is now available in Ubuntu releases. > > 2. But dump capture is still not successful with case1 fix as the system > is reseting, if some CPUs > are not responding to IPIs, instead of booting into KDump kernel. > > While case1 is resolved - the kernel doesn't hang anymore if some CPUs don't > respond to IPIs. As for > case2, I suspect the reset could be happening in f/w while reinitializing > CPUs. Need to confirm that > though. Also, exploring if it is possible to workaround what seems like a > firwmare limitation. Please > keep the bug open while I work on case2. If we can't workaround case2, may > have to close this as > will-not-fix.
While this is on my TODO list, putting this low on my priority list as it is an unlikely user scenario... Thanks Hari -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1680349 Title: Kdump fails to capture dump on Firestone NV when machine crashes while running stress-ng. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1680349/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
