[Bug 1942784] Re: makedumpfile not properly working on focal with 5.11 kernel

[Ioanna Alifieraki]

Tested new debdiff on Focal with 5.4 and 5.11 kernels, on amd64, arm64, ppc64el and s390x and
works as expected.
Making Hirsute 'Invalid' as all patches in new debdiff are already in H.

** Changed in: makedumpfile (Ubuntu Hirsute)
       Status: In Progress => Invalid

-- 
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/1942784

Title:
  makedumpfile not properly working on focal with 5.11 kernel

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Focal:
  In Progress
Status in makedumpfile source package in Hirsute:
  Invalid

Bug description:
  [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 f1197543d1c4 ([PATCH] Retrieve MAX_PHYSMEM_BITS from vmcoreinfo).
  The reason for falling back to cp is that without this patch makedumpfile calculates wrongly the memory layout.
  This happens after the kernel commit 1d50e5d0c505 ("crash_core, vmcoreinfo: Append 'MAX_PHYSMEM_BITS'to vmcoreinfo").
  With this commit applied, reading MAX_PHYSMEM_BITS from vmcoreinfo instead of inferring lead to correctly detecting the memory layout and creating the dump file properly. 

  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1942784/+subscriptions