[Bug 1879214] Re: Package makedumpfile 1:1.6.7-1ubuntu2(arm64) failed to makedumpfile:calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported

Ioanna Alifieraki 1879214 at bugs.launchpad.net
Thu Apr 15 19:57:08 UTC 2021


Debdiff for Focal V2.

** Patch added: "lp1879214_focal_v2.debdiff"
   https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1879214/+attachment/5488488/+files/lp1879214_focal_v2.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1879214

Title:
  Package makedumpfile 1:1.6.7-1ubuntu2(arm64) failed to
  makedumpfile:calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47
  not supported

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Bionic:
  Confirmed
Status in makedumpfile source package in Focal:
  Confirmed
Status in makedumpfile source package in Groovy:
  Confirmed
Status in makedumpfile source package in Hirsute:
  Fix Released
Status in makedumpfile package in Debian:
  Fix Released

Bug description:
  [Impact]

  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
  https://github.com/makedumpfile/makedumpfile/commit/d8b701796f0491f2ac4b06c7a5b795c29399efab

  [PATCH 2/3] arm64: Make use of NUMBER(VA_BITS) in vmcoreinfo
  https://github.com/makedumpfile/makedumpfile/commit/67d0e1d68f28c567a704fd6b9b8fd696ad3df183

  [PATCH 3/3] arm64: support flipped VA and 52-bit kernel VA
  https://github.com/makedumpfile/makedumpfile/commit/a0216b678a95f099a16172cc4a67ad5aa6a89583

  [Test Case]

  OS: Ubuntu 20.04 LTS
  kernel: 5.4.0-21-generic
  arch:arm64
  Description:
  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[653]: Starting kdump-tools:
  [   26.612761] kdump-tools[659]: Starting kdump-tools:
  [   26.628565] kdump-tools[659]: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/2020050
  [   26.648621] kdump-tools[676]: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/2020050
  [   26.668445] kdump-tools[676]: calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported
  [   26.678199] kdump-tools[676]: get_machdep_info_arm64
  [   26.692518] kdump-tools[659]: get_machdep_info_arm64
  [   26.852221] hns3 0000:7d:00.0: get link status cmd failed -16

  [   94.351303] kdump-tools[659]: * kdump-tools: makedumpfile failed, * kdump-tools: saved vmcore in /var/crash/202005061048
  [   94.435510] kdump-tools[659]:  * running makedumpfile --dump-dmesg /proc/vmcore /var/crash/202005061048/dmesg.202005061048
  [   94.457103] kdump-tools[688]: calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported
  [   94.476228] kdump-tools[688]: get_machdep_info_arm64: Can't determine platform config values
  [   94.485912] kdump-tools[688]: makedumpfile Failed.
  [   94.500760] kdump-tools[659]:  * kdump-tools: makedumpfile --dump-dmesg failed. dmesg content will be unavailable
  [   94.520225] kdump-tools[659]:  * kdump-tools: failed to save dmesg content in /var/crash/202005061048
  [   94.544205] kdump-tools[691]: Wed, 06 May 2020 10:49:42 -0400
  [   94.564597] kdump-tools[692]: Rebooting.
  [   94.678709] reboot: Restarting systemlpc uart init Done

  [Regression Potential]

  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
  arm64 only
  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
  arm64 only
  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.

  [Other]

  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
  needed :

  commit da0d25ffa585c9a1adb94562c815daa393b1ee5e
  [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:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1879214/+subscriptions



More information about the Ubuntu-sponsors mailing list