| Message ID | 20180430165713.19837-1-gwalbon@linux.vnet.ibm.com |
|---|---|
| Headers | show |
| Series | IBM Boston CPU hardlockup | expand |
On 04/30/18 18:57, Gustavo Walbon wrote: > BugLink: http://bugs.launchpad.net/bugs/1767927 > > == SRU Justification == > In few tests of validation of firmware was detected this issue which > triggers a hardlockup that was fixed through an update for firmware > in the skiboot project and this patchset in the kernel side. > > All patches were merged on the upstream kernel v4.17-rc1. > > Nicholas Piggin (3): > powerpc/powernv: Handle unknown OPAL errors in opal_nvram_write() > powerpc/64s: return more carefully from sreset NMI > powerpc/64s: sreset panic if there is no debugger or crash dump > handlers > > arch/powerpc/include/asm/hw_irq.h | 8 ++++ > arch/powerpc/include/asm/paca.h | 1 + > arch/powerpc/kernel/asm-offsets.c | 1 + > arch/powerpc/kernel/exceptions-64s.S | 61 +++++++++++++++++++++++++++-- > arch/powerpc/kernel/traps.c | 15 ++++++- > arch/powerpc/platforms/powernv/opal-nvram.c | 4 ++ > 6 files changed, 85 insertions(+), 5 deletions(-) > From the comments made on the original IBM bug it seems that a fourth patch has been sent upstream but not accepted. The patches are limited to the powerpc architecture, so provided that IBM tests the changes for regressions and make sure the three patches are sufficient once they reach a build in -proposed: Acked-by: Kleber Sacilotto de Souza <kleber.souza@canonical.com>
On 30.04.2018 18:57, Gustavo Walbon wrote: > BugLink: http://bugs.launchpad.net/bugs/1767927 > > == SRU Justification == > In few tests of validation of firmware was detected this issue which > triggers a hardlockup that was fixed through an update for firmware > in the skiboot project and this patchset in the kernel side. > > All patches were merged on the upstream kernel v4.17-rc1. > > Nicholas Piggin (3): > powerpc/powernv: Handle unknown OPAL errors in opal_nvram_write() > powerpc/64s: return more carefully from sreset NMI > powerpc/64s: sreset panic if there is no debugger or crash dump > handlers > > arch/powerpc/include/asm/hw_irq.h | 8 ++++ > arch/powerpc/include/asm/paca.h | 1 + > arch/powerpc/kernel/asm-offsets.c | 1 + > arch/powerpc/kernel/exceptions-64s.S | 61 +++++++++++++++++++++++++++-- > arch/powerpc/kernel/traps.c | 15 ++++++- > arch/powerpc/platforms/powernv/opal-nvram.c | 4 ++ > 6 files changed, 85 insertions(+), 5 deletions(-) > Agreeing with Kleber... Acked-by: Stefan Bader <stefan.bader@canonical.com>
Applied the 3 patches to bionic master-next. -Stefan
BugLink: http://bugs.launchpad.net/bugs/1767927 == SRU Justification == In few tests of validation of firmware was detected this issue which triggers a hardlockup that was fixed through an update for firmware in the skiboot project and this patchset in the kernel side. All patches were merged on the upstream kernel v4.17-rc1. Nicholas Piggin (3): powerpc/powernv: Handle unknown OPAL errors in opal_nvram_write() powerpc/64s: return more carefully from sreset NMI powerpc/64s: sreset panic if there is no debugger or crash dump handlers arch/powerpc/include/asm/hw_irq.h | 8 ++++ arch/powerpc/include/asm/paca.h | 1 + arch/powerpc/kernel/asm-offsets.c | 1 + arch/powerpc/kernel/exceptions-64s.S | 61 +++++++++++++++++++++++++++-- arch/powerpc/kernel/traps.c | 15 ++++++- arch/powerpc/platforms/powernv/opal-nvram.c | 4 ++ 6 files changed, 85 insertions(+), 5 deletions(-)