Linux* Kernel Panic Records 
System Event Log Troubleshooting Guide for EPSD
 
Platforms Based on Intel
®
 Xeon
®
 Processor E5 4600/2600/2400/1600/1400 Product Families 
130  Intel order number G90620-002  Revision 1.1 
15.  Linux* Kernel Panic Records 
The Open IPMI driver supports the ability to put semi-custom and custom events in the system event log if a panic occurs. If you 
enable the “Generate a panic event to all BMCs on a panic” option, you will get one event on a panic in a standard IPMI event format. 
If you enable the “Generate OEM events containing the panic string” option, you will also get a set of OEM events holding the panic 
string. 
Table 105: Linux* Kernel Panic Event Record Characteristics 
The first byte of the panic string (0 if no panic string) 
Event Direction and Event Type 
[7] Event direction 
0b = Assertion Event 
1b = Deassertion Event 
[6:0] Event Type = 6Fh (Sensor Specific) 
[7:6] – 10b = OEM code in Event Data 2 
[5:4] – 10b = OEM code in Event Data 3 
[3:0] – Event Trigger Offset = 1h = Runtime Critical Stop (a.k.a. “core dump”, “blue screen”) 
The second byte of the panic string 
The third byte of the panic string