** Changed in: makedumpfile (Debian)
Status: Unknown => Fix Released
--
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/1763532
Title:
set reasonable default cmdlines for arm64
Status in kexec-tools package in Ubuntu:
New
Status in makedumpfile package in Ubuntu:
New
Status in kexec-tools source package in Xenial:
New
Status in makedumpfile source package in Xenial:
New
Status in kexec-tools source package in Artful:
New
Status in makedumpfile source package in Artful:
New
Status in makedumpfile package in Debian:
Fix Released
Bug description:
[Impact]
Crash dump support doesn't work by default on any known arm64 platform. Users
have to figure out working incantations for the crashkernel= parameter and the
parameters passed to the crash-dump kernel themselves and manual edit 2
different config files.
[Test Case]
Using either a Centriq 2400 or a Cavium ThunderX CRB (these platforms are
known to support crashdump), and with a kernel >= 4.13 (xenial-ga did not
support crashdump):
sudo apt install kdump-tools
(reboot, so crashkernel= is added to the kernel commandline)
echo c | sudo tee /proc/sysrq-trigger
Crash dump should occur, with artifacts collected in /var/crash.
If you want to verify that the dump is usable, install the
corresponding linux-image-<ver>-dbgsym package and run:
sudo crash /usr/lib/debug/boot/vmlinux-<ver>
/var/crash/<crash>/dump.<crash>
crash should successfully load, placing you at a "crash>" prompt. At that
prompt, you can issue the 'bt' command to see a backtrace.
Note: you need crash from zesty (7.1.8-1ubuntu1) or later.
[Regression Risk]
TBD
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1763532/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
