IPMI Event Code: A080124900E00140 0000000000000000
Record Type = E0h
Reporting Entity ID = System Firmware - cabinet 0, cell slot 0, cpu 0
Event ID = #4681
...........................................................
Keyword = BOOT_STOP_BOOT_OVERRIDE
Description:
The user has manually bypassed a stop boot condition (caused by an error during boot) and continued to boot an O/S. The system might experience unpredictable failures.
Cause / Action:
The user has initiated manual O/S boot despite the existence of a error.
Recommendation:
Correct the error condition (see output of "INFO WARNING" EFI shell command), reboot the system, and then initiate O/S boot.
___________________________________________________________
Timestamp flag = 1 - The next record is the timestamp for this one
Alert Level = 5 - Critical
Data Type = 0 - Data field unused
Data = 00 00 00 00 00 00 00 00
_______________________________________________________________________________
IPMI Event Code: C14F6500C5020130 FF3F4070000F0300
Timestamp (GMT) = Sat Mar 17 21:23:17 2012
Generator id: System Software ID = 0
Event message format = IPMI version 1.0
Sensor
Number Triplet Data 2 Data 3
------ -------- ------ ------
00 0F:70:40 3F FF
Decoding as system type: Merlion
Sensor Number : Various, refer to manual
Sensor Type = System Firmware Progress (aka POST Error)
Event type = Assertion event : OEM defined
System Firmware Error (POST Error)
reserved
___________________________________________________________
Alert Level = 5 - Critical
_______________________________________________________________________________
IPMI Event Code: 778002F100E00110 0000000000000000
Record Type = E0h
Reporting Entity ID = System Firmware - cabinet 0, cell slot 0, cpu 0
Event ID = #753
...........................................................
Keyword = EFI_SYSID_INVALID
Description:
The system ID(s) currently in the system is either invalid or, if the EFI_SYSID_BMC_WARNING, EFI_SYSID_BMC_READ_ERROR or EFI_SYSID_BMC_WRITE_ERROR events are also present, inaccessible to the system firmware. A stop boot condition will be generated and software license will probably be invalid.
Data Field: 64-bit value.
If preceded by 0xbad00000000000 the following valid values are possible:
0000 -> valid UUID (should never see this one)
0001 -> magic UUID
0002 -> inaccessible UUID
0004 -> invalid (bad CRC) UUID
If zero, then one of the following conditions occurred:
Invalid combination of primary and secondary system ID values
User declined copying/entering system ID values when prompted by firmware
All other values indicate failure during attempt to update system IDs.
Cause / Action:
The system ID(s) is invalid and the user did not elect to fix the problem.
Recommendation:
Reboot the system and follow the prompts to fix the issue.
----- WTEC Note -------------------------------------------
Note :
Primary System ID resides on the system board
Invalid System Type, SystemType = 10
Can't say where Secondary System ID is stored
For additional information, including how to resolve these errors, refer to
http://wtec.cup.hp.com/~cpuhw/IA64/cookbook/sysid_loc.htm ___________________________________________________________
Timestamp flag = 1 - The next record is the timestamp for this one
Alert Level = 3 - Warning or non-critical
Data Type = 23 - Status return from function call
Data = 00 00 00 00 00 00 00 00
看起来是刷BIOS刷出问题了哟!