[Bug 1879214] Please test proposed package
1879214 at bugs.launchpad.net
Mon Apr 26 09:15:39 UTC 2021
Hello chenrongwen, or anyone else affected,
Accepted makedumpfile into bionic-proposed. The package will build now
and be available at
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
bionic to verification-done-bionic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-bionic. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
Package makedumpfile 1:1.6.7-1ubuntu2(arm64) failed to
makedumpfile:calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47
Status in makedumpfile package in Ubuntu:
Status in makedumpfile source package in Bionic:
Status in makedumpfile source package in Focal:
Status in makedumpfile source package in Groovy:
Status in makedumpfile source package in Hirsute:
Status in makedumpfile package in Debian:
On arm64 and kernels 5.4+ makedumpfile fails.
Upstream patches solve this bug :
[PATCH 1/3] Use vmcoreinfo note in /proc/kcore for --mem-usage option
[PATCH 2/3] arm64: Make use of NUMBER(VA_BITS) in vmcoreinfo
[PATCH 3/3] arm64: support flipped VA and 52-bit kernel VA
OS: Ubuntu 20.04 LTS
When testing kdump on Ubuntu 20.04 LTS (arm64), makedumpfile fails. The test steps are as follows:
# echo 1> / proc / sys / kernel / sysrq
# echo c> / proc / sysrq-trigger
The error logs are as follows:
[ 26.599161] kdump-tools: Starting kdump-tools:
[ 26.612761] kdump-tools: Starting kdump-tools:
[ 26.628565] kdump-tools: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/2020050
[ 26.648621] kdump-tools: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/2020050
[ 26.668445] kdump-tools: calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported
[ 26.678199] kdump-tools: get_machdep_info_arm64
[ 26.692518] kdump-tools: get_machdep_info_arm64
[ 26.852221] hns3 0000:7d:00.0: get link status cmd failed -16
[ 94.351303] kdump-tools: * kdump-tools: makedumpfile failed, * kdump-tools: saved vmcore in /var/crash/202005061048
[ 94.435510] kdump-tools: * running makedumpfile --dump-dmesg /proc/vmcore /var/crash/202005061048/dmesg.202005061048
[ 94.457103] kdump-tools: calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported
[ 94.476228] kdump-tools: get_machdep_info_arm64: Can't determine platform config values
[ 94.485912] kdump-tools: makedumpfile Failed.
[ 94.500760] kdump-tools: * kdump-tools: makedumpfile --dump-dmesg failed. dmesg content will be unavailable
[ 94.520225] kdump-tools: * kdump-tools: failed to save dmesg content in /var/crash/202005061048
[ 94.544205] kdump-tools: Wed, 06 May 2020 10:49:42 -0400
[ 94.564597] kdump-tools: Rebooting.
[ 94.678709] reboot: Restarting systemlpc uart init Done
Patch 1 : [PATCH 1/3] Use vmcoreinfo note in /proc/kcore for --mem-usage option
removes get_elf_loads function this function was only used with --mem-usage option
, since kernel commit kernel commit 23c85094fe18 (kernel versions >4.19)
the information needed is in vmcoreinfo
Any regression potential would affect the --mem-usage only
Patch 2 : [PATCH 2/3] arm64: Make use of NUMBER(VA_BITS) in vmcoreinfo
make use of NUMBER(VA_BITS) in vmcoreinfo as the current way of guessing VA_BITS
does not work on Linux 5.4 and later.
Before this commit VA_BITS would be calculated in get_versiondep_info_arm64, however
this way of calculation breaks after 5.4. This commit gets the VA_BITS from vmcoreinfo
and as a safeguard it uses the old way of deriving VA_BITS only if reading from vmcoreinfo doesn't work.
From the kernel side VA_BITS is in vmcoreinfo since kernel 4.12, F and later use later kernel so not
great regression potentional and if any it would only affect arm64.
Patch 3 : [PATCH 3/3] arm64: support flipped VA and 52-bit kernel VA
Linux 5.4 and later kernels for arm64 changed the kernel VA space
arrangement and introduced 52-bit kernel VAs by merging branch
commit b333b0ba2346. Support 5.9+ kernels with vmcoreinfo entries
and 5.4+ kernels with best guessing.
This patch makes adjustemnt to properly calculate vabits_actual, max_physmem_bits, page_offset
Any regression potential would affect only arm64 and the calculation of the above variables.
For H only the 3 commits are needed and they cherry-pick.
For G and F the 3rd commit does not apply and an extra commit is
[PATCH] arm64: Add support for ARMv8.2-LPA (52-bit PA support)
This bug also affects Bionic when 5.4 hwe kernel is used.
To manage notifications about this bug go to:
More information about the Ubuntu-sponsors