You have been subscribed to a public bug by Ioanna Alifieraki (joalif):
[IMPACT]
When running Focal with the hwe 5.11 kernel makedumpfile is not working as it
should.
Instead of compressing the dump makedumpfile falls back to cp.
This can create problems on systems with very large RAM and result into
exhausting all storage on the host.
This can be resolved with upstream commit 54aec3878b3f([PATCH] make use of
'uts_namespace.name' offset in VMCOREINFO).
In addition the dmesg.<timestamp> is not created.
This can be resolved with the following two commits :
- commit c617ec633392([PATCH 1/2] printk: add support for lockless ringbuffer)
- commit 44b073b7ec46([PATCH 2/2] printk: use committed/finalized state values)
[TEST CASE]
For testing a machine running focal with the 5.11 kernel is required.
Then trigger a crash.
On the console we can see that makedumpfile fails and `falls back to cp`.
In /var/crash we can see that no dmesg file is created and instead of the dump
file
the uncompressed vmcoreinfo is created.
[WHERE PROBLEMS COULD OCCUR]
The 3 commits pulled into focal make makedumpfile compatible with the 5.11
kernel.
Any regression potential would involve the crash dump not being created after a
crash in case kdump is configured.
[OTHER]
Only Focal with 5.11 kernel is affected.
** Affects: makedumpfile (Ubuntu)
Importance: Undecided
Status: New
** Affects: makedumpfile (Ubuntu Focal)
Importance: Medium
Assignee: Ioanna Alifieraki (joalif)
Status: Confirmed
--
makedumpfile not properly working on focal with 5.11 kernel
https://bugs.launchpad.net/bugs/1942784
You received this bug notification because you are a member of STS Sponsors,
which is subscribed to the bug report.
--
Mailing list: https://launchpad.net/~sts-sponsors
Post to : sts-sponsors@lists.launchpad.net
Unsubscribe : https://launchpad.net/~sts-sponsors
More help : https://help.launchpad.net/ListHelp
