| 2020-05-18 02:25:02 |
chenrongwen |
bug |
|
|
added bug |
| 2020-05-18 02:25:02 |
chenrongwen |
attachment added |
|
error.log https://bugs.launchpad.net/bugs/1879214/+attachment/5373123/+files/error.log |
|
| 2020-05-18 02:30:28 |
chenrongwen |
attachment added |
|
sosreport-ubuntu-1879214-2020-05-18-dqmztlf.tar.xz https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1879214/+attachment/5373124/+files/sosreport-ubuntu-1879214-2020-05-18-dqmztlf.tar.xz |
|
| 2020-05-18 14:53:12 |
Guilherme G. Piccoli |
bug |
|
|
added subscriber Guilherme G. Piccoli |
| 2020-06-15 19:21:45 |
Guilherme G. Piccoli |
makedumpfile (Ubuntu): status |
New |
Confirmed |
|
| 2020-07-02 07:52:05 |
tonihu |
bug |
|
|
added subscriber tonihu |
| 2020-07-14 15:29:10 |
Ioanna Alifieraki |
makedumpfile (Ubuntu): assignee |
|
Ioanna Alifieraki (joalif) |
|
| 2020-07-14 15:29:21 |
Ioanna Alifieraki |
tags |
makedumpfile |
makedumpfile sts |
|
| 2020-12-27 22:02:29 |
Dominique Poulain |
bug |
|
|
added subscriber Dominique Poulain |
| 2021-03-03 17:25:15 |
Ioanna Alifieraki |
nominated for series |
|
Ubuntu Focal |
|
| 2021-03-03 17:25:15 |
Ioanna Alifieraki |
bug task added |
|
makedumpfile (Ubuntu Focal) |
|
| 2021-03-03 17:25:15 |
Ioanna Alifieraki |
nominated for series |
|
Ubuntu Hirsute |
|
| 2021-03-03 17:25:15 |
Ioanna Alifieraki |
bug task added |
|
makedumpfile (Ubuntu Hirsute) |
|
| 2021-03-03 17:25:15 |
Ioanna Alifieraki |
nominated for series |
|
Ubuntu Groovy |
|
| 2021-03-03 17:25:15 |
Ioanna Alifieraki |
bug task added |
|
makedumpfile (Ubuntu Groovy) |
|
| 2021-03-03 17:32:23 |
Ioanna Alifieraki |
description |
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 |
[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] |
|
| 2021-03-03 21:37:18 |
Ioanna Alifieraki |
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] |
[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) |
|
| 2021-03-03 21:37:23 |
Ioanna Alifieraki |
makedumpfile (Ubuntu Groovy): status |
New |
Confirmed |
|
| 2021-03-03 21:37:27 |
Ioanna Alifieraki |
makedumpfile (Ubuntu Focal): status |
New |
Confirmed |
|
| 2021-03-03 21:38:05 |
Ioanna Alifieraki |
attachment added |
|
lp1879214_hirsute.debdiff https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1879214/+attachment/5472235/+files/lp1879214_hirsute.debdiff |
|
| 2021-03-03 21:38:09 |
Ioanna Alifieraki |
attachment added |
|
lp1879214_hirsute.debdiff https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1879214/+attachment/5472236/+files/lp1879214_hirsute.debdiff |
|
| 2021-03-03 21:38:42 |
Ioanna Alifieraki |
attachment added |
|
lp1879214_groovy.debdiff https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1879214/+attachment/5472237/+files/lp1879214_groovy.debdiff |
|
| 2021-03-03 21:39:09 |
Ioanna Alifieraki |
attachment added |
|
lp1879214_focal.debdiff https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1879214/+attachment/5472238/+files/lp1879214_focal.debdiff |
|
| 2021-03-04 00:33:40 |
Ubuntu Foundations Team Bug Bot |
tags |
makedumpfile sts |
makedumpfile patch sts |
|
| 2021-03-04 00:33:48 |
Ubuntu Foundations Team Bug Bot |
bug |
|
|
added subscriber Ubuntu Sponsors Team |
| 2021-03-06 23:13:16 |
Mathew Hodson |
makedumpfile (Ubuntu Focal): importance |
Undecided |
High |
|
| 2021-03-06 23:13:18 |
Mathew Hodson |
makedumpfile (Ubuntu Groovy): importance |
Undecided |
High |
|
| 2021-03-06 23:13:21 |
Mathew Hodson |
makedumpfile (Ubuntu Hirsute): importance |
Undecided |
High |
|
| 2021-03-10 23:32:38 |
David Duncan |
bug |
|
|
added subscriber David Duncan |
| 2021-03-11 12:52:11 |
Pedro Principeza |
bug |
|
|
added subscriber Pedro Principeza |
| 2021-04-07 19:59:16 |
Ioanna Alifieraki |
bug watch added |
|
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986594 |
|
| 2021-04-07 19:59:16 |
Ioanna Alifieraki |
bug task added |
|
makedumpfile (Debian) |
|
| 2021-04-07 19:59:34 |
Ioanna Alifieraki |
makedumpfile (Ubuntu Groovy): assignee |
|
Ioanna Alifieraki (joalif) |
|
| 2021-04-07 19:59:36 |
Ioanna Alifieraki |
makedumpfile (Ubuntu Focal): assignee |
|
Ioanna Alifieraki (joalif) |
|
| 2021-04-08 00:27:25 |
Bug Watch Updater |
makedumpfile (Debian): status |
Unknown |
Fix Released |
|
| 2021-04-09 15:21:33 |
Launchpad Janitor |
makedumpfile (Ubuntu Hirsute): status |
Confirmed |
Fix Released |
|
| 2021-04-13 13:07:46 |
Ioanna Alifieraki |
attachment added |
|
lp1879214_bionic.debdiff https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1879214/+attachment/5487329/+files/lp1879214_bionic.debdiff |
|
| 2021-04-13 13:07:59 |
Ioanna Alifieraki |
nominated for series |
|
Ubuntu Bionic |
|
| 2021-04-13 13:07:59 |
Ioanna Alifieraki |
bug task added |
|
makedumpfile (Ubuntu Bionic) |
|
| 2021-04-13 13:08:13 |
Ioanna Alifieraki |
makedumpfile (Ubuntu Bionic): status |
New |
Confirmed |
|
| 2021-04-13 13:09:10 |
Ioanna Alifieraki |
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) |
[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. |
|
| 2021-04-15 19:56:32 |
Ioanna Alifieraki |
attachment added |
|
lp1879214_groovy_v2.debdiff https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1879214/+attachment/5488487/+files/lp1879214_groovy_v2.debdiff |
|
| 2021-04-15 19:57:08 |
Ioanna Alifieraki |
attachment added |
|
lp1879214_focal_v2.debdiff https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1879214/+attachment/5488488/+files/lp1879214_focal_v2.debdiff |
|
| 2021-04-15 19:57:43 |
Ioanna Alifieraki |
attachment added |
|
lp1879214_bionic_v2.debdiff https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1879214/+attachment/5488489/+files/lp1879214_bionic_v2.debdiff |
|
| 2021-04-26 09:03:45 |
Timo Aaltonen |
makedumpfile (Ubuntu Focal): status |
Confirmed |
Fix Committed |
|
| 2021-04-26 09:03:47 |
Timo Aaltonen |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2021-04-26 09:03:50 |
Timo Aaltonen |
bug |
|
|
added subscriber SRU Verification |
| 2021-04-26 09:03:54 |
Timo Aaltonen |
tags |
makedumpfile patch sts |
makedumpfile patch sts verification-needed verification-needed-focal |
|
| 2021-04-26 09:11:32 |
Timo Aaltonen |
makedumpfile (Ubuntu Groovy): status |
Confirmed |
Fix Committed |
|
| 2021-04-26 09:11:41 |
Timo Aaltonen |
tags |
makedumpfile patch sts verification-needed verification-needed-focal |
makedumpfile patch sts verification-needed verification-needed-focal verification-needed-groovy |
|
| 2021-04-26 09:15:31 |
Timo Aaltonen |
makedumpfile (Ubuntu Bionic): status |
Confirmed |
Fix Committed |
|
| 2021-04-26 09:15:38 |
Timo Aaltonen |
tags |
makedumpfile patch sts verification-needed verification-needed-focal verification-needed-groovy |
makedumpfile patch sts verification-needed verification-needed-bionic verification-needed-focal verification-needed-groovy |
|
| 2021-04-26 11:07:17 |
Ioanna Alifieraki |
tags |
makedumpfile patch sts verification-needed verification-needed-bionic verification-needed-focal verification-needed-groovy |
makedumpfile patch sts verification-done verification-done-bionic verification-done-focal verification-done-groovy |
|
| 2021-05-02 02:54:52 |
Mathew Hodson |
makedumpfile (Ubuntu Bionic): importance |
Undecided |
High |
|
| 2021-05-06 08:30:43 |
Launchpad Janitor |
makedumpfile (Ubuntu Groovy): status |
Fix Committed |
Fix Released |
|
| 2021-05-06 08:30:49 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2021-05-06 08:51:18 |
Launchpad Janitor |
makedumpfile (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
| 2021-05-06 08:59:59 |
Launchpad Janitor |
makedumpfile (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
