[Kernel-packages] [Bug 1751835] Re: Ubuntu 18.04 kdump does not work on bionic-proposed 4.15 ppc64el with AC922
*** This bug is a duplicate of bug 1743529 ***
https://bugs.launchpad.net/bugs/1743529
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: kexec-tools (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1751835
Title:
Ubuntu 18.04 kdump does not work on bionic-proposed 4.15 ppc64el with
AC922
Status in The Ubuntu-power-systems project:
New
Status in kexec-tools package in Ubuntu:
Confirmed
Bug description:
no guest was running, only Ubuntu 18.04 Host installed and trying
kdump only on the host
===
tried on the ubuntu released proposed kernel 4.15.0-10-generic and kdump
process was able to proceed (did not dump complete vmcore though) but hit
issue, please check below console log
root@ltciofvtr-spoon4:~# dmesg | grep -i crash
[0.00] Reserving 6144MB of memory at 128MB for crashkernel (System
RAM: 524288MB)
[0.00] Kernel command line:
root=UUID=749429f9-83b9-4776-9a3e-147e297cdf99 ro quiet splash crashkernel=6144M
root@ltciofvtr-spoon4:~# dmesg | grep -i reserv
[0.00] Reserving 6144MB of memory at 128MB for crashkernel (System
RAM: 524288MB)
[0.00] cma: Reserved 26224 MiB at 0x20399500
[0.00] DMA zone: 0 pages reserved
[0.00] DMA zone: 0 pages reserved
[0.00] Memory: 502952192K/536870912K available (13376K kernel code,
2048K rwdata, 3648K rodata, 4800K init, 3037K bss, 7065344K reserved, 26853376K
cma-reserved)
root@ltciofvtr-spoon4:~# uname -a
Linux ltciofvtr-spoon4 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:21:52
UTC 2018 ppc64le ppc64le ppc64le GNU/Linux
root@ltciofvtr-spoon4:~# kdump
kdump kdump-config
root@ltciofvtr-spoon4:~# kdump
kdump kdump-config
root@ltciofvtr-spoon4:~# kdump-config
Usage: /usr/sbin/kdump-config
{help|test|show|status|load|unload|savecore|propagate|symlinks kernel-version}
root@ltciofvtr-spoon4:~# kdump-config status
current state : ready to kdump
root@ltciofvtr-spoon4:~# echo 1 > /proc/sys/kernel/sysrq
root@ltciofvtr-spoon4:~# echo c > /proc/sysrq-trigger
[ 164.604204] sysrq: SysRq : Trigger a crash
[ 164.604264] Unable to handle kernel paging request for data at address
0x
[ 164.604395] Faulting instruction address: 0xc07ea268
[ 164.604481] Oops: Kernel access of bad area, sig: 11 [#1]
[ 164.604559] LE SMP NR_CPUS=2048 NUMA PowerNV
[ 164.604628] Modules linked in: idt_89hpesx ofpart ipmi_powernv
ipmi_devintf ipmi_msghandler ibmpowernv cmdlinepart vmx_crypto powernv_flash
at24 uio_pdrv_genirq uio mtd opal_prd crct10dif_vpmsum sch_fq_codel ip_tables
x_tables autofs4 mlx5_ib ib_core mlx5_core bnx2x ast i2c_algo_bit ttm
drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops mdio ahci mlxfw
libcrc32c crc32c_vpmsum drm tg3 libahci devlink
[ 164.605176] CPU: 72 PID: 3444 Comm: bash Not tainted 4.15.0-10-generic
#11-Ubuntu
[ 164.605305] NIP: c07ea268 LR: c07eb1a8 CTR:
c07ea240
[ 164.605413] REGS: c0002038f8c2f9f0 TRAP: 0300 Not tainted
(4.15.0-10-generic)
[ 164.605496] MSR: 90009033 CR: 2822
XER: 2004
[ 164.605641] CFAR: c07eb1a4 DAR: DSISR: 4200
SOFTE: 1
[ 164.605641] GPR00: c07eb1a8 c0002038f8c2fc70 c16ea600
0063
[ 164.605641] GPR04: c000203993d0ce18 c000203993d24368 90009033
0808
[ 164.605641] GPR08: 0007 0001
90001003
[ 164.605641] GPR12: c07ea240 c7a51800 08f7fbb8e008
[ 164.605641] GPR16: 08f7fb19e9f0 08f7fb231998 08f7fb2319d0
08f7fb268204
[ 164.605641] GPR20: 0001
7fffed1e1b54
[ 164.605641] GPR24: 7fffed1e1b50 08f7fb26afc4 c15e9930
0002
[ 164.605641] GPR28: 0063 0004 c1572a9c
c15e9cd0
[ 164.606714] NIP [c07ea268] sysrq_handle_crash+0x28/0x30
[ 164.606796] LR [c07eb1a8] __handle_sysrq+0xf8/0x2c0
[ 164.606865] Call Trace:
[ 164.606919] [c0002038f8c2fc70] [c07eb188]
__handle_sysrq+0xd8/0x2c0 (unreliable)
[ 164.607043] [c0002038f8c2fd10] [c07eb9b4]
write_sysrq_trigger+0x64/0x90
[ 164.607152] [c0002038f8c2fd40] [c047c548] proc_reg_write+0x88/0xd0
[ 164.607252] [c0002038f8c2fd70] [c03cf8dc] __vfs_write+0x3c/0x70
[ 164.607347] [c0002038f8c2fd90] [c03cfb38] vfs_write+0xd8/0x220
[ 164.607445] [c0002038f8c2fde0] [c03cfe58] SyS_write+0x68/0x110
[ 164.607545] [c0002038f8c2fe30] [c000b184] system_call+0x58/0x6c
[ 164.607640] Instruction dump:
[ 164.607689] 4bfff9f1
[Kernel-packages] [Bug 1751835] Re: Ubuntu 18.04 kdump does not work on bionic-proposed 4.15 ppc64el with AC922
*** This bug is a duplicate of bug 1743529 ***
https://bugs.launchpad.net/bugs/1743529
This is a duplicate of LP#1743529. As mentioned there, latest kexec-
tools has been merged from Debian, as is awaiting for sponsorship. It is
available from my personal ppa for testing.
Cascardo.
** This bug has been marked a duplicate of bug 1743529
Merge kexec-tools 2.0.16-1 from Debian: System hung with Kernel panic -not
syncing: Out of memory message when crash is triggered.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1751835
Title:
Ubuntu 18.04 kdump does not work on bionic-proposed 4.15 ppc64el with
AC922
Status in The Ubuntu-power-systems project:
New
Status in kexec-tools package in Ubuntu:
New
Bug description:
no guest was running, only Ubuntu 18.04 Host installed and trying
kdump only on the host
===
tried on the ubuntu released proposed kernel 4.15.0-10-generic and kdump
process was able to proceed (did not dump complete vmcore though) but hit
issue, please check below console log
root@ltciofvtr-spoon4:~# dmesg | grep -i crash
[0.00] Reserving 6144MB of memory at 128MB for crashkernel (System
RAM: 524288MB)
[0.00] Kernel command line:
root=UUID=749429f9-83b9-4776-9a3e-147e297cdf99 ro quiet splash crashkernel=6144M
root@ltciofvtr-spoon4:~# dmesg | grep -i reserv
[0.00] Reserving 6144MB of memory at 128MB for crashkernel (System
RAM: 524288MB)
[0.00] cma: Reserved 26224 MiB at 0x20399500
[0.00] DMA zone: 0 pages reserved
[0.00] DMA zone: 0 pages reserved
[0.00] Memory: 502952192K/536870912K available (13376K kernel code,
2048K rwdata, 3648K rodata, 4800K init, 3037K bss, 7065344K reserved, 26853376K
cma-reserved)
root@ltciofvtr-spoon4:~# uname -a
Linux ltciofvtr-spoon4 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:21:52
UTC 2018 ppc64le ppc64le ppc64le GNU/Linux
root@ltciofvtr-spoon4:~# kdump
kdump kdump-config
root@ltciofvtr-spoon4:~# kdump
kdump kdump-config
root@ltciofvtr-spoon4:~# kdump-config
Usage: /usr/sbin/kdump-config
{help|test|show|status|load|unload|savecore|propagate|symlinks kernel-version}
root@ltciofvtr-spoon4:~# kdump-config status
current state : ready to kdump
root@ltciofvtr-spoon4:~# echo 1 > /proc/sys/kernel/sysrq
root@ltciofvtr-spoon4:~# echo c > /proc/sysrq-trigger
[ 164.604204] sysrq: SysRq : Trigger a crash
[ 164.604264] Unable to handle kernel paging request for data at address
0x
[ 164.604395] Faulting instruction address: 0xc07ea268
[ 164.604481] Oops: Kernel access of bad area, sig: 11 [#1]
[ 164.604559] LE SMP NR_CPUS=2048 NUMA PowerNV
[ 164.604628] Modules linked in: idt_89hpesx ofpart ipmi_powernv
ipmi_devintf ipmi_msghandler ibmpowernv cmdlinepart vmx_crypto powernv_flash
at24 uio_pdrv_genirq uio mtd opal_prd crct10dif_vpmsum sch_fq_codel ip_tables
x_tables autofs4 mlx5_ib ib_core mlx5_core bnx2x ast i2c_algo_bit ttm
drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops mdio ahci mlxfw
libcrc32c crc32c_vpmsum drm tg3 libahci devlink
[ 164.605176] CPU: 72 PID: 3444 Comm: bash Not tainted 4.15.0-10-generic
#11-Ubuntu
[ 164.605305] NIP: c07ea268 LR: c07eb1a8 CTR:
c07ea240
[ 164.605413] REGS: c0002038f8c2f9f0 TRAP: 0300 Not tainted
(4.15.0-10-generic)
[ 164.605496] MSR: 90009033 CR: 2822
XER: 2004
[ 164.605641] CFAR: c07eb1a4 DAR: DSISR: 4200
SOFTE: 1
[ 164.605641] GPR00: c07eb1a8 c0002038f8c2fc70 c16ea600
0063
[ 164.605641] GPR04: c000203993d0ce18 c000203993d24368 90009033
0808
[ 164.605641] GPR08: 0007 0001
90001003
[ 164.605641] GPR12: c07ea240 c7a51800 08f7fbb8e008
[ 164.605641] GPR16: 08f7fb19e9f0 08f7fb231998 08f7fb2319d0
08f7fb268204
[ 164.605641] GPR20: 0001
7fffed1e1b54
[ 164.605641] GPR24: 7fffed1e1b50 08f7fb26afc4 c15e9930
0002
[ 164.605641] GPR28: 0063 0004 c1572a9c
c15e9cd0
[ 164.606714] NIP [c07ea268] sysrq_handle_crash+0x28/0x30
[ 164.606796] LR [c07eb1a8] __handle_sysrq+0xf8/0x2c0
[ 164.606865] Call Trace:
[ 164.606919] [c0002038f8c2fc70] [c07eb188]
__handle_sysrq+0xd8/0x2c0 (unreliable)
[ 164.607043] [c0002038f8c2fd10] [c07eb9b4]
write_sysrq_trigger+0x64/0x90
[ 164.607152] [c0002038f8c2fd40] [c047c548] proc_reg_write+0x88/0xd0
[ 164.607252] [c0002038f8c2fd70] [c03cf8dc] __vfs_write+0x3c/0x70
[ 164.607347]
[Kernel-packages] [Bug 1751835] Re: Ubuntu 18.04 kdump does not work on bionic-proposed 4.15 ppc64el with AC922
** Also affects: ubuntu-power-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-power-systems
Importance: Undecided => Critical
** Changed in: ubuntu-power-systems
Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)
** Tags added: triage-g
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1751835
Title:
Ubuntu 18.04 kdump does not work on bionic-proposed 4.15 ppc64el with
AC922
Status in The Ubuntu-power-systems project:
New
Status in kexec-tools package in Ubuntu:
New
Bug description:
no guest was running, only Ubuntu 18.04 Host installed and trying
kdump only on the host
===
tried on the ubuntu released proposed kernel 4.15.0-10-generic and kdump
process was able to proceed (did not dump complete vmcore though) but hit
issue, please check below console log
root@ltciofvtr-spoon4:~# dmesg | grep -i crash
[0.00] Reserving 6144MB of memory at 128MB for crashkernel (System
RAM: 524288MB)
[0.00] Kernel command line:
root=UUID=749429f9-83b9-4776-9a3e-147e297cdf99 ro quiet splash crashkernel=6144M
root@ltciofvtr-spoon4:~# dmesg | grep -i reserv
[0.00] Reserving 6144MB of memory at 128MB for crashkernel (System
RAM: 524288MB)
[0.00] cma: Reserved 26224 MiB at 0x20399500
[0.00] DMA zone: 0 pages reserved
[0.00] DMA zone: 0 pages reserved
[0.00] Memory: 502952192K/536870912K available (13376K kernel code,
2048K rwdata, 3648K rodata, 4800K init, 3037K bss, 7065344K reserved, 26853376K
cma-reserved)
root@ltciofvtr-spoon4:~# uname -a
Linux ltciofvtr-spoon4 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:21:52
UTC 2018 ppc64le ppc64le ppc64le GNU/Linux
root@ltciofvtr-spoon4:~# kdump
kdump kdump-config
root@ltciofvtr-spoon4:~# kdump
kdump kdump-config
root@ltciofvtr-spoon4:~# kdump-config
Usage: /usr/sbin/kdump-config
{help|test|show|status|load|unload|savecore|propagate|symlinks kernel-version}
root@ltciofvtr-spoon4:~# kdump-config status
current state : ready to kdump
root@ltciofvtr-spoon4:~# echo 1 > /proc/sys/kernel/sysrq
root@ltciofvtr-spoon4:~# echo c > /proc/sysrq-trigger
[ 164.604204] sysrq: SysRq : Trigger a crash
[ 164.604264] Unable to handle kernel paging request for data at address
0x
[ 164.604395] Faulting instruction address: 0xc07ea268
[ 164.604481] Oops: Kernel access of bad area, sig: 11 [#1]
[ 164.604559] LE SMP NR_CPUS=2048 NUMA PowerNV
[ 164.604628] Modules linked in: idt_89hpesx ofpart ipmi_powernv
ipmi_devintf ipmi_msghandler ibmpowernv cmdlinepart vmx_crypto powernv_flash
at24 uio_pdrv_genirq uio mtd opal_prd crct10dif_vpmsum sch_fq_codel ip_tables
x_tables autofs4 mlx5_ib ib_core mlx5_core bnx2x ast i2c_algo_bit ttm
drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops mdio ahci mlxfw
libcrc32c crc32c_vpmsum drm tg3 libahci devlink
[ 164.605176] CPU: 72 PID: 3444 Comm: bash Not tainted 4.15.0-10-generic
#11-Ubuntu
[ 164.605305] NIP: c07ea268 LR: c07eb1a8 CTR:
c07ea240
[ 164.605413] REGS: c0002038f8c2f9f0 TRAP: 0300 Not tainted
(4.15.0-10-generic)
[ 164.605496] MSR: 90009033 CR: 2822
XER: 2004
[ 164.605641] CFAR: c07eb1a4 DAR: DSISR: 4200
SOFTE: 1
[ 164.605641] GPR00: c07eb1a8 c0002038f8c2fc70 c16ea600
0063
[ 164.605641] GPR04: c000203993d0ce18 c000203993d24368 90009033
0808
[ 164.605641] GPR08: 0007 0001
90001003
[ 164.605641] GPR12: c07ea240 c7a51800 08f7fbb8e008
[ 164.605641] GPR16: 08f7fb19e9f0 08f7fb231998 08f7fb2319d0
08f7fb268204
[ 164.605641] GPR20: 0001
7fffed1e1b54
[ 164.605641] GPR24: 7fffed1e1b50 08f7fb26afc4 c15e9930
0002
[ 164.605641] GPR28: 0063 0004 c1572a9c
c15e9cd0
[ 164.606714] NIP [c07ea268] sysrq_handle_crash+0x28/0x30
[ 164.606796] LR [c07eb1a8] __handle_sysrq+0xf8/0x2c0
[ 164.606865] Call Trace:
[ 164.606919] [c0002038f8c2fc70] [c07eb188]
__handle_sysrq+0xd8/0x2c0 (unreliable)
[ 164.607043] [c0002038f8c2fd10] [c07eb9b4]
write_sysrq_trigger+0x64/0x90
[ 164.607152] [c0002038f8c2fd40] [c047c548] proc_reg_write+0x88/0xd0
[ 164.607252] [c0002038f8c2fd70] [c03cf8dc] __vfs_write+0x3c/0x70
[ 164.607347] [c0002038f8c2fd90] [c03cfb38] vfs_write+0xd8/0x220
[ 164.607445] [c0002038f8c2fde0] [c03cfe58] SyS_write+0x68/0x110
[ 164.607545] [c0002038f8c2fe30] [c000b184]
