Test results for both makedumpfile --dump-dmesg and for the crash utility for the log -P option that the patch that adds the caller_id field to the log records printed if the log caller_id field is present in the dump have been posted to the crash utllity git hub Issue list: https://github.com/crash-utility/crash/issues/164 I have a patch submitted upstream to makedumpfile (makedumpfile Issue-13) that provides PRINTK_CALLER id support for makedumpfile. That makedumpfile patch is needed to test the crash facility since to provides the support to produce vmcore files that include the caller_id field for log records. So that is why I also include output from makedumpfie --dump-dmesg so that you can compare the makedumpfile output for the makedumpfile --dump-dmesg command versus the output crash log -P produces to print out the dmesg records. Note that I tested and provide results for two Linux Kernels: linux-5.4.256 and linux-6.6.6 The reason for this is to cover the two versions of the Linux kernel ringbuffer that provide PRINTK_CALLER support the versions for printk_log and printk_info. There are two versions because PRINTK_CALLER id support as provided by the CONFIG_PRINTK_CALLER kernel configuration parameter that was added in Linux-5.1 which is using the printk_log internal structure. The newer printk_caller structure used by the lockless ringbuffer was added in Linux 5.10 and has been in use ever since and this structure replaced the older printk_log structure with the printk_info structure. So Linux-5.4.264 covers the older printk_log internal structure format and Linux-6.6.6 covers the newer printk_info internal structure format of the Linux ringbuffer. The testing output files created using the crash patch posted as mentioned at the crash-utility git hub Issues list at: https://github.com/crash-utility/crash/issues/164 (as gzipped files) and also posted at the makedumpfile github Issues list at makedumpfile Issue-13. To produce vmcore files with the PRINTK_CALLER id requires the patch provided to makedumpfile Issue-13 That patch is also posted to the crash utility github Issues site at: https://github.com/crash-utility/crash/issues/164 (as a gzipped file: makedumpfile-add-dmesg-PRINTK_CALLER-id-support-rev3.patch.gz) The patch applies and builds with the latest makedumpfile git hub code For dmesg output using enhanced makedumpfile 1.7.4++ output used command: makedumpfile --dump-dmesg -- Crash-utility mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxxxxxx https://${domain_name}/admin/lists/devel.lists.crash-utility.osci.io/ Contribution Guidelines: https://github.com/crash-utility/crash/wiki
