** Changed in: kexec-tools (Ubuntu Xenial)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: makedumpfile (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: makedumpfile (Ubuntu Xenial)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: makedumpfile (Ubuntu Zesty)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
--
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/1694859
Title:
arm64 kernel crashdump support
Status in kexec-tools package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Fix Committed
Status in makedumpfile package in Ubuntu:
Confirmed
Status in kexec-tools source package in Xenial:
Confirmed
Status in linux source package in Xenial:
Won't Fix
Status in makedumpfile source package in Xenial:
Confirmed
Status in kexec-tools source package in Yakkety:
Confirmed
Status in linux source package in Yakkety:
Won't Fix
Status in makedumpfile source package in Yakkety:
Confirmed
Status in kexec-tools source package in Zesty:
In Progress
Status in linux source package in Zesty:
Fix Committed
Status in makedumpfile source package in Zesty:
Confirmed
Bug description:
Note: Updates are being staged at ppa:dannf/arm64-kdump.
[Impact]
It is not possible to collect a kernel crash dump from a crashed arm64 server
for later debugging.
[Test Case]
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.
[Regression Risk]
3 patches here touch code outside of arch/arm64/:
memblock: add memblock_clear_nomap()
This adds a new function with no callers, so regression risk is negligible.
(A later patch adds a call to it under arch/arm64/).
memblock: add memblock_cap_memory_range()
This refactors some of the code in memblock_mem_limit_remove_map() into a new
function. The only existing caller of memblock_mem_limit_remove_map() is under
arch/arm64/, so the regression risk outside of arm64 is negligible.
efi/libstub/arm*: Set default address and size cells values for an empty dtb
Because this code is for EFI platforms that support device-tree, it is
de-facto ARM-specific (as noted in the patch title).
For arm64, we have mitigated the risk by explicit regression testing on
several platforms:
- Qualcomm QDF2400
- Cavium ThunderX CRB1S
- HP m400 (X-Gene)
- HiSilicon D05 (Hi07)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1694859/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
