kdump-tools uses the wrong crashkernel command line parameter in ppc64le
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
The Ubuntu-power-systems project |
Fix Released
|
High
|
Manoj Iyer | ||
makedumpfile (Debian) |
Fix Released
|
Unknown
|
|||
makedumpfile (Ubuntu) |
Fix Released
|
High
|
Canonical Kernel Team |
Bug Description
== Comment: #0 - Thiago Jung Bauermann <email address hidden> - 2017-03-24 11:44:39 ==
---Problem Description---
kdump-tools uses the wrong crashkernel command line parameter in ppc64le:
u1704le?? grep crashkernel /boot/grub/grub.cfg
128M of reserved memory is too small for ppc64le.
That happens because /etc/default/
u1704le?? ls -l /etc/default/
total 8.0K
lrwxrwxrwx 1 root root 39 Mar 24 13:34 kdump-tools.cfg -> /etc/default/
-rw-r--r-- 1 root root 80 Jan 5 08:07 kdump-tools.default
-rw-r--r-- 1 root root 137 Jan 5 08:07 kdump-tools.
u1704le??
As can be seen, it should be pointing to kdump-tools.
Also, kdump-tools.
Possibly just a cosmetic issue, but it would be nice if that was fixed.
Contact Information = <email address hidden>
---uname output---
Linux u1704le 4.10.0-13-generic #15-Ubuntu SMP Thu Mar 9 20:27:28 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux
Machine Type = Any ppc64le machine. In this case, a KVM guest hosted on an 8286-42A.
---Debugger---
A debugger is not configured
---Steps to Reproduce---
sudo apt intall kdump-tools
Select 'Yes' when asked whether kdump should be enabled.
Userspace tool common name: kdump
The userspace tool has the following bit modes: 64 bit
Userspace rpm: kdump-tools
Userspace tool obtained from project website: na
*Additional Instructions for <email address hidden>:
-Attach ltrace and strace of userspace application.
tags: | added: architecture-ppc64le bugnameltc-152905 severity-medium targetmilestone-inin1704 |
Changed in ubuntu: | |
assignee: | nobody → Taco Screen team (taco-screen-team) |
affects: | ubuntu → makedumpfile (Ubuntu) |
Changed in makedumpfile (Ubuntu): | |
assignee: | Taco Screen team (taco-screen-team) → Nish Aravamudan (nacc) |
importance: | Undecided → High |
tags: | added: ubuntu-17.04 |
Changed in makedumpfile (Debian): | |
status: | Unknown → New |
Changed in ubuntu-power-systems: | |
importance: | Undecided → High |
tags: | added: triage-a |
Changed in makedumpfile (Ubuntu): | |
assignee: | Nish Aravamudan (nacc) → nobody |
Changed in makedumpfile (Ubuntu): | |
assignee: | nobody → Canonical Kernel Team (canonical-kernel-team) |
Changed in makedumpfile (Debian): | |
status: | New → Fix Released |
Changed in ubuntu-power-systems: | |
assignee: | nobody → Manoj Iyer (manjo) |
Changed in ubuntu-power-systems: | |
status: | New → Fix Released |
tags: |
added: triage-g removed: triage-a |
Hello,
Well, this is to be expected as the postinst script will only change the target of the symlink if the architecture is ppc64EL and not ppc64LE ( EL != LE).
Now if both are interchangeable (I must admit my ignorance of this architecture), I don't mind fixing the script to apply to both EL and LE.