(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 fi
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 no
(In reply to comment #66)
> debian.master/config/ppc64el/config.common.ppc64el:CONFIG_PANIC_TIMEOUT=10
>
> is now set to non '0' value for Xenial, Artful and Bionic.
Thanks for this fix as it resolves the hang...
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
(In reply to comment #70)
> Default Comment by Bridge
>
> Default Comment by Bridge
>
> Default Comment by Bridge
>
> Default Comment by Bridge
>
> Following comment #31, could you confirm that this is resolved with the 4.15
> kernel in Bionic?
Issue is observed even on 18.04 [ 4.15.0-12-generic ]
(In reply to comment #65)
> We believe this issue is resolved in Artful (17.10), could you please
> validate before we close this bug?
Issue is observed even on 17.10.
md.unit=kdump-tools.service ata_piix.prefer_ms_hyperv=0 elfcorehdr=157184K
* loaded kdump kernel
root@ltc-firep3:~# kdump-config
--- Comment From hbath...@in.ibm.com 2017-07-31 14:20 EDT---
(In reply to comment #51)
> I believe this request should be routed to the kernel team (setting of a
> kernel default value for POWER systems)?
Some CPUs are entering hang state by the time of crash.
There are two sides to look a
