sts-sponsors team mailing list archive

Thread
Date

[Bug 1921403] Re: makedumpfile does not create dmesg file in /var/crash on 5.10+ kernels

To: sts-sponsors@xxxxxxxxxxxxxxxxxxx
From: Launchpad Bug Tracker <1921403@xxxxxxxxxxxxxxxxxx>
Date: Thu, 04 Nov 2021 22:19:17 -0000
Reply-to: Bug 1921403 <1921403@xxxxxxxxxxxxxxxxxx>
Sender: noreply@xxxxxxxxxxxxx

This bug was fixed in the package makedumpfile - 1:1.6.7-1ubuntu2.3

---------------
makedumpfile (1:1.6.7-1ubuntu2.3) focal; urgency=medium

  * makedumpfile falls back to cp with the 5.11 kernel (LP: #1942784)
    -d/p/0008-PATCH-Retrieve-MAX_PHYSMEM_BITS-from-vmcoreinfo.patch
  * makedumpfile doesn't create dmesg file on 5.10+ kernels (LP: #1921403)
    -d/p/0009-PATCH-1-2-printk-add-support-for-lockless-ringbuffer.patch
    -d/p/0010-PATCH-2-2-printk-use-committed-finalized-state-value.patch

 -- Ioanna Alifieraki <ioanna-maria.alifieraki@xxxxxxxxxxxxx>  Mon, 18
Oct 2021 16:43:56 +0000

** Changed in: makedumpfile (Ubuntu Focal)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1921403

Title:
  makedumpfile does not create dmesg file in /var/crash on 5.10+ kernels

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Focal:
  Fix Released
Status in makedumpfile source package in Hirsute:
  Fix Released
Status in makedumpfile package in Debian:
  Fix Released

Bug description:
  [IMPACT]
  makedumpfile does not create the dmesg.<timestamp> in /var/crash.
  This happens only on 5.10+ kernel because 5.10 kernel introduces a new
  lockless ringbuffer.

  This issue has been addressed upstream with commits :
  [1] c617ec633392([PATCH 1/2] printk: add support for lockless ringbuffer)
  [2] 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.
  After reboot make sure that dmesg.<timestamp> file is created in /var/crash/<timestamp>

  [WHERE PROBLEMS COULD OCCUR]

  Any problems would involve the dmesg file not created.

  [Other]

  [1] https://github.com/makedumpfile/makedumpfile/commit/c617ec63339222f3a44d73e36677a9acc8954ccd
  [2] https://github.com/makedumpfile/makedumpfile/commit/44b073b7ec467aee0d7de381d455b8ace1199184

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