This bug was fixed in the package crash - 7.2.8-1ubuntu1.20.10.2
---------------
crash (7.2.8-1ubuntu1.20.10.2) groovy; urgency=medium
* Fix FTBFS (LP: #1931435):
- d/p/0004-Fix-for-an-ARM64-gcc-10-compilation-error.-Without-t.patch
crash (7.2.8-1ubuntu1.20.10.1) groovy; urgency=medium
* Fix cannot determine VA_BITS_ACTUAL (LP: #1919275):
- d/p/0003-arm64-Change-tcr_el1_t1sz-variable-name-to-TCR_EL1_T.patch
-- Ioanna Alifieraki <ioanna-maria.alifier...@canonical.com> Thu, 10
Jun 2021 16:07:41 +0000
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
https://bugs.launchpad.net/bugs/1919275
Title:
crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL
Status in crash package in Ubuntu:
New
Status in linux package in Ubuntu:
Incomplete
Status in crash source package in Bionic:
Fix Released
Status in linux source package in Bionic:
Invalid
Status in crash source package in Focal:
Fix Released
Status in linux source package in Focal:
Fix Released
Status in crash source package in Groovy:
Fix Released
Status in linux source package in Groovy:
Fix Released
Bug description:
[Impact]
On Ubuntu Bionic with the 5.4.0-1038-aws kernel the crash utility
7.2.8-1ubuntu0.18.04 fails with:
crash: cannot determine VA_BITS_ACTUAL
This bug has been addressed upstream and needed patches both in crash
and kernel.
Kernel patch :
commit bbdbc11804ff0b4130e7550113b452e96a74d16e
Author: Bhupesh Sharma <bhsha...@redhat.com>
Date: Thu May 14 00:22:37 2020 +0530
arm64/crash_core: Export TCR_EL1.T1SZ in vmcoreinfo
Crash patch :
commit 1c45cea02df7f947b4296c1dcaefa1024235ef10
Author: Bhupesh Sharma <bhsha...@redhat.com>
Date: Tue Jul 14 01:14:49 2020 +0530
arm64: Change tcr_el1_t1sz variable name to TCR_EL1_T1SZ
Series affected :
Kenrel :
This affects Focal (5.4 kernel) and Groovy (5.8 kernel).
Hirsute already contains the commit and kernels prior to 5.3 are not affected.
Crash :
The commit is already in Hirsute.
Groovy, Focal and Bionic are affected.
In case of Bionic the bug appears only if 5.4 hwe kernel is used.
[Test Case]
On an arm64 host which runs the affected releases and kernels after creating
a crashdump try to open it with crash.
It will fail with :
crash: cannot determine VA_BITS_ACTUAL
[Where problems could occur]
Kernel patch :
The kernel patch reads the appropriate cpu register and exports TCR_EL1.T1SZ
variable in vmcoreinfo. Given that this is a simple operation
and that this patch landed upstream in 5.9 and no regressions have been
reported, it is safe to assume that the regression potential is minimal.
Any potential problem would occur in vmcoreinfo since this is where
TCR_EL1.T1SZ variable is exported.
Crash patch :
This patch renames tcr_el1_t1sz variable to TCR_EL1_T1SZ to be compatible
with the kernel change above for crash to be able to read it.
The regression potential is small and any problem would regard reading this
variable.
[Other]
Workaround :
This bug/change in crash provides a workaround for 5.4+
https://github.com/crash-utility/crash/issues/52 kernels.
While it appears as though it this was fixed it
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1858958 it still
doesn't seem to work with a 5.4 kernel including. I also tested
https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu0.18.04.1/+build/18807621/+files/crash_7.2.8-1ubuntu0.18.04.1_arm64.deb
and it exhibits the same problem.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+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
