** Description changed: + [IMPACT] - [DESCRIPTION] 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
** Tags added: sts -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921403 Title: makedumpfile does not create dmesg file in /var/crash on 5.10+ kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1921403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
