diff options
| author | David Gibson <david@gibson.dropbear.id.au> | 2017-12-04 16:27:25 +1100 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2017-12-14 09:52:57 +0100 |
| commit | d46be2f67c1088077e35ab87da6fc2b0d367fb88 (patch) | |
| tree | 8de20ba790c8b98c984b61d38cb8e94c2712f941 /drivers/gpio | |
| parent | 59d97bf77a98adb08ce98073842374f17d7876de (diff) | |
| download | linux-stable-d46be2f67c1088077e35ab87da6fc2b0d367fb88.tar.gz linux-stable-d46be2f67c1088077e35ab87da6fc2b0d367fb88.tar.bz2 linux-stable-d46be2f67c1088077e35ab87da6fc2b0d367fb88.zip | |
Revert "powerpc: Do not call ppc_md.panic in fadump panic notifier"
commit ab9dbf771ff9b6b7e814e759213ed01d7f0de320 upstream.
This reverts commit a3b2cb30f252b21a6f962e0dd107c8b897ca65e4.
That commit tried to fix problems with panic on powerpc in certain
circumstances, where some output from the generic panic code was being
dropped.
Unfortunately, it breaks things worse in other circumstances. In
particular when running a PAPR guest, it will now attempt to reboot
instead of informing the hypervisor (KVM or PowerVM) that the guest
has crashed. The crash notification is important to some
virtualization management layers.
Revert it for now until we can come up with a better solution.
Fixes: a3b2cb30f252 ("powerpc: Do not call ppc_md.panic in fadump panic notifier")
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
[mpe: Tweak change log a bit]
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/gpio')
0 files changed, 0 insertions, 0 deletions