- 论坛徽章:
- 0
|
IPMI Event Code: F480009806E00320 000000000000000B
Record Type = E0h
Reporting Entity ID = System Firmware - cpu 6
Event ID = #152
...........................................................
Keyword = MC_INITIATED
Description:
A Machine Check has been initiated
Cause / Action:
A Machine Check has occurred.
Recommendation:
Analyze cause of Machine Check using diag's and EFI tools.
___________________________________________________________
Alert Level = 7 - Fatal
Data Type = 20 - Major change in state
For details, see 4.2.20 of Event Architecture Specification
Data = 00 00 00 00 00 00 00 0B
_______________________________________________________________________________
IPMI Event Code: C151C23C67020310 003FA17000130300
Timestamp (GMT) = Wed Jun 19 23:19:03 2013
Generator = System Software ID = 0
Alert Level = 7 - Fatal
Sensor
Number Triplet Data 2 Data 3
------ -------- ------ ------
00 13:70:A1 3F 00
Decoding as system type: Ruby/Sapphire
Sensor Number : 00 - Various, refer to manual
Sensor Type : 13 = Critical Interrupt
Event type = Assertion event : OEM defined
Keyword = MACHINE_CHECK_INITIATED
Machine Check initiated. Processor = 00
Go to the EFI shell and do
Shell> errdump mca 'filename'
where filename is any name you like. This file can then be run
through the MCA analyser tool
A Machine Check Abort event means the hardware detected a critical error. This event is generated
whenever a system error due to processor, firmware, hardware and operating system is encountered.
MCA events may be either recoverable or non-recoverable. If it is recoverable, the system will
attempt to recover from the error for the purpose of maintaining high availability. An example of
which is automatic disabling of a failing processor. For non-recoverable errors, the system will
either stop or reboot to prevent data corruption and unreliable operation
你把MCA的文件和你的升级过程日志发过来看看呢 |
|
免费注册
发表于 2013-06-30 18:17