How to identify the thread ID or CPU ID that issued a printk() to the kernel ring buffer from a vmcore

Solution Verified - Updated -

Issue

  • How to identify the thread ID (TID) or CPU ID that issued a printk() call to write messages to the kernel ring buffer (dmesg) from a vmcore.

  • How to determine which thread accessed /dev/watchdog0, leading to watchdog timeout messages and a kernel panic:

[105351.966765] watchdog: watchdog0: watchdog did not stop!
[105351.966841] watchdog: watchdog0: watchdog did not stop!
[105373.209527] Kernel panic - not syncing: 06: An NMI occurred. Depending on your system the reason for the NMI is logged in any one of the following resources:
[105373.209531] 1. Integrated Management Log (IML)
[105373.209532] 2. OA Syslog
[105373.209533] 3. OA Forward Progress Log
[105373.209533] 4. iLO Event Log

Environment

  • Red Hat Enterprise Linux 8
  • Red Hat Enterprise Linux 9
  • Red Hat Enterprise Linux 10
  • vmcore
  • crash

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content