** Description changed:
## FFE ##
[ Rationale ]
* makedumpfile and crash need to stay compatible with the Linux kernel
version. Since our stonking kernel moved to 7.2, makedumpfile 1.7.7 and
crash 9.0.2+~16.3 are no longer compatible with new crashdumps from
kernel 7.2. The packages need updates to makedumpfile 1.7.9 (plus a
post-1.7.9 patch) and crash 9.0.3+~16.3.
[ Scope ]
* For crash, version 9.0.3+~16.3 is needed to resolve this issue. A
commit from the upstream 9.0.3 release partially resolves this issue:
3a415c0 ("symbols: Add support for mod symtab with combined GPL and non-GPL
symbols")
https://github.com/crash-utility/crash/commit/3a415c07a18a465df2580365b43b4d8f8a5d815b
* A makedumpfile update to version 1.7.9 is also needed, but there's an
additional post-1.7.9 patch needed too:
f50c015 ("f50c015f150f93dc69f813eb6d966b2a102140b3") [PATCH] Fix wrong
exclusion of compound tail pages on Linux 7.1 and later
https://github.com/makedumpfile/makedumpfile/commit/f50c015f150f93dc69f813eb6d966b2a102140b3
* crash merge request:
https://code.launchpad.net/~kevinbecker/ubuntu/+source/crash/+git/crash/+merge/511377
* makedumpfile merge request:
https://code.launchpad.net/~kevinbecker/ubuntu/+source/makedumpfile/+git/makedumpfile/+merge/511378
* seeded-in-ubuntu output:
crash (from crash) is seeded in:
- ubuntu-core-installer: daily-live
+ ubuntu-core-installer: daily-live
makedumpfile (from makedumpfile) is seeded in:
- ubuntu-core-installer: daily-live
-
+ ubuntu-core-installer: daily-live
[ Regression Potential ]
* If there was a regression here, it would be evident in the processing
a crashdump with the crash tool. It should not affect any other usage.
[ Testing ]
* PPA:
https://launchpad.net/~kevinbecker/+archive/ubuntu/crash-makedumpfile-lp2167256
* Autopkgtest
* Manual test plan
- - Install kdump-tools update on stonking from PPA above
- - Reboot
- - Confirm kdump is configured with `kdump-config show`. If it isn't, do it
manually ( https://ubuntu.com/server/docs/how-to/software/kernel-crash-dump/ )
- - Take a dump manually ( # echo c > /proc/sysrq-trigger )
- - The crash dump should be taken now and the system should reboot
- - Confirm the dump exists in /var/crash
- - Install kernel debug symbols
- - Open crashdump with crash tool
+ - Install kdump-tools
+ - Install makedumpfile and crash from PPA above
+ - Reboot
+ - Confirm kdump is configured with `kdump-config show`. If it isn't, do it
manually ( https://ubuntu.com/server/docs/how-to/software/kernel-crash-dump/ )
+ - Take a dump manually ( # echo c > /proc/sysrq-trigger )
+ - The crash dump should be taken now and the system should reboot
+ - Confirm the dump exists in /var/crash
+ - Install kernel debug symbols
+ - Open crashdump with crash tool
[ Other Info ]
* I plan to get these changes into Debian in the future, but didn't have
the time to get it there first before stonking.
[ Original Description ]
crash version 9.0.2 with makedumpfile 1.7.7 in stonking fails to open
crash dumps from new 7.2 kernels.
Steps to reproduce:
1. Setup the kernel and dbgsym packages
2. Install kdump-tools
3. Following error is noticed:
```
$ crash
...
warning: Section .debug_names in
/usr/lib/debug/boot/vmlinux-7.2.0-5-generic length 135272 does not match
section length 313176, ignoring .debug_names.
WARNING: SLUB: cannot determine how compound pages are linked
please wait... (gathering module symbol data)
crash: invalid structure member offset: module_num_gpl_syms
FILE: kernel.c LINE: 3834 FUNCTION: module_init()
[/usr/bin/crash] error trace: 5ab695c064c4 => 5ab695e0acb6 => 5ab695ea8ba3 =>
5ab695f48ac8
```
A commit from the upstream 9.0.3 release partially resolves this issue:
3a415c0 ("symbols: Add support for mod symtab with combined GPL and non-GPL
symbols")
https://github.com/crash-utility/crash/commit/3a415c07a18a465df2580365b43b4d8f8a5d815b
This commit makes the error go away, but crash still doesn't load the
dump correctly on amd64. However, it does work on s390x.
A makedumpfile update is needed too. Updating from makedumpfile 1.7.7 to
makedumpfile 1.7.9 plus the following patch does fix it:
f50c015 ("f50c015f150f93dc69f813eb6d966b2a102140b3") [PATCH] Fix wrong
exclusion of compound tail pages on Linux 7.1 and later
https://github.com/makedumpfile/makedumpfile/commit/f50c015f150f93dc69f813eb6d966b2a102140b3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2167256
Title:
[FFe] Crash fails to open crashdumps from kernel 7.2 on stonking
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/2167256/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
