You have been subscribed to a public bug by Mauricio Faria de Oliveira (mfo):
[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. [FIX] 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 ** Affects: makedumpfile (Ubuntu) Importance: Undecided Assignee: Ioanna Alifieraki (joalif) Status: Fix Released ** Affects: makedumpfile (Ubuntu Focal) Importance: Medium Assignee: Ioanna Alifieraki (joalif) Status: In Progress ** Affects: makedumpfile (Ubuntu Hirsute) Importance: Medium Assignee: Ioanna Alifieraki (joalif) Status: Fix Released ** Affects: makedumpfile (Debian) Importance: Unknown Status: Fix Released ** Tags: sts sts-sponsor-mfo -- makedumpfile does not create dmesg file in /var/crash on 5.10+ kernels https://bugs.launchpad.net/bugs/1921403 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 : [email protected] Unsubscribe : https://launchpad.net/~sts-sponsors More help : https://help.launchpad.net/ListHelp
