ISST-LTE:pVM:roselp4:ubuntu 17.04: kdump failed after memory DLPAR
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
The Ubuntu-power-systems project |
New
|
High
|
Canonical Kernel Team | ||
linux (Ubuntu) |
New
|
High
|
Canonical Kernel Team |
Bug Description
---Problem Description---
After a memory DLPAR removal, kdump doesn't work:
Starting Kernel crash dump capture service...
[ 67.714593] kdump-tools[3850]: Starting kdump-tools: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/
Copying data : [ 2.1 %] -/usr/sbin/
[ 72.314140] kdump-tools[3850]: * kdump-tools: makedumpfile failed, falling back to 'cp'
[ 73.693881] kdump-tools[3850]: cp: error reading '/proc/vmcore': Bad address
[ 73.704152] kdump-tools[3850]: * kdump-tools: failed to save vmcore in /var/crash/
[ 73.823643] kdump-tools[3850]: * running makedumpfile --dump-dmesg /proc/vmcore /var/crash/
[ 73.973813] kdump-tools[3850]: The kernel version is not supported.
[ 73.974078] kdump-tools[3850]: The makedumpfile operation may be incomplete.
[ 73.983506] kdump-tools[3850]: The dmesg log is saved to /var/crash/
[ 73.983752] kdump-tools[3850]: makedumpfile Completed.
[ 73.983998] kdump-tools[3850]: * kdump-tools: saved dmesg content in /var/crash/
[ 74.104555] kdump-tools[3850]: Thu, 23 Feb 2017 00:05:15 -0600
[ 74.233502] kdump-tools[3850]: Failed to read reboot parameter file: No such file or directory
[ 74.233782] kdump-tools[3850]: Rebooting.
[ 86.629777] reboot: Restarting system
The kdump service should be restarted after the memory DLPAR operation.
C
---uname output---
Linux roselp4 4.10.0-8-generic #10-Ubuntu SMP Mon Feb 13 14:00:06 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux
Machine Type = lpar
---Debugger---
A debugger is not configured
---Steps to Reproduce---
1. config kdump on roselp4
2. do a memory DLPAR removal operation
3. trigger kdump
tags: | added: architecture-ppc64le bugnameltc-151960 severity-high targetmilestone-inin--- |
Changed in ubuntu: | |
assignee: | nobody → Taco Screen team (taco-screen-team) |
affects: | ubuntu → linux (Ubuntu) |
tags: |
added: targetmilestone-inin1704 removed: targetmilestone-inin--- |
Changed in linux (Ubuntu): | |
assignee: | Taco Screen team (taco-screen-team) → Nish Aravamudan (nacc) |
importance: | Undecided → High |
tags: | added: ubuntu-17.04 |
Changed in ubuntu-power-systems: | |
importance: | Undecided → High |
tags: | added: triage-a |
Changed in linux (Ubuntu): | |
assignee: | Nish Aravamudan (nacc) → nobody |
tags: |
added: kernel-key removed: kernel-da-key |
Changed in linux (Ubuntu): | |
assignee: | nobody → Canonical Kernel Team (canonical-kernel-team) |
tags: |
added: kernel-da-key removed: kernel-key |
Changed in ubuntu-power-systems: | |
assignee: | nobody → Canonical Kernel Team (canonical-kernel-team) |
tags: |
added: triage-r removed: triage-a |
tags: | added: cscc |
/proc/vmcore is generated by kdump support in the kernel. This might not be a bug, but a case of missing support for regenerating /proc/vmcore entries after DLPAR memory removal.