topic rx4640 mp log in Integrity Servers

rx4640 mp log

upbboy — Tue, 06 May 2008 01:16:16 GMT

hi everyone

we have rx4640
We found mp error log from that machine.
But I don't know about this.
Please let me know it's mean.

thank you

Alert Level 3: Warning
Keyword: HP-UX_DUMP_STATUS
OS dump status (EFxx)
A memory dump occurred on the system, or on one partition in a cellular system. The dump occurred due to either a non-recoverable error
or by user request. EFxx is the OS dump status (the success/failure of the writing of the dump). EF00 = success (followed by either EF0A
= successful dump with sync, or EF09 = successful dump without sync), EFFF = a general error, EFFE = dump path assertion failure, EFFD
= no dump was taken by default, choice or failure, EFFC = dump was aborted by user.
Logged by: HP-UX Kernel cabinet 0, slot 0, cpu 0
Legacy PA HEX Chassis Code = 0xaef00
Data: 0x3f00033900e00000 0x00000000000aef00

Log Entry 4070: Mon May 5 06:04:12 2008
Alert Level 3: Warning
Keyword: HP-UX_CRASHDUMP_STARTED
OS crashdump started (D700)
Logged by: HP-UX Kernel cabinet 0, slot 0, cpu 0
Legacy PA HEX Chassis Code = 0xad700
Data: 0x7f80033700e00ea0 0x00000000000ad700
Time: 0x6b00033700e00eb0 0x01000000481ea35c

SL (,+,-,?,F,L,J,D,K,R,T,V,A,C,U,q) >
Log Entry 4068: Mon May 5 06:04:10 2008
Alert Level 5: Critical
Keyword: HP-UX_HEX_FAULT_CODE
OS legacy PA hex fault code (Bxxx)
OS legacy PA hex fault code (Bxxx). Possible I/O error or system panic
Logged by: HP-UX Kernel cabinet 0, slot 0, cpu 0
Legacy PA HEX Chassis Code = 0x2b000
Data: 0xbf80033800e00e80 0x000000000002b000
Time: 0xab00033800e00e90 0x01000000481ea35a

Log Entry 4066:
Alert Level 7: Fatal
Keyword: OS_CRITICAL_SHUTDOWN
OS run-time critical shutdown
Logged by: Baseboard Management Controller
Data: 0x21481ea359020e70 0xff0f016f00200300
Mon May 5 06:04:09 2008
Generator: OS Agent
Sensor Type: OS Critical Stop
Sensor Number: 0

SL (,+,-,?,F,L,J,D,K,R,T,V,A,C,U,q) >
Log Entry 4057: Mon May 5 06:04:08 2008
Alert Level 7: Fatal
Keyword: INIT_INITIATED
INIT initiated
This is the equivalent of a TOC event in the PA RISC Architecture. On IPF systems, this event is called an INIT. This event can be trigg
ered by the "tc" command from the MP, or from the button labeled "TOC" or "Transfer of Control" on the Management card or bezel of the s
ystem. There are also other causes of an INIT generated by software. Data: Local CPU Number
Logged by: System Firmware cabinet 0, slot 0, cpu 1
System State = 1(Boot Complete)
State Change Event = 0(At BIB)
LED Command Valid = 0(LED state is not updated)
LED Run = 0(off (default))
LED Attention = 0(reserved)
LED Stopped = 0(off (default))
Data: 0xf480007901e00e50 0x0000000000000001
Time: 0xeb00007901e00e60 0x01000000481ea358

Re: rx4640 mp log

Sameer_Nirmal — Tue, 06 May 2008 02:45:22 GMT

The sequence of the MP event logs shows that the system had a panic on account of an INIT. When the system was rebooted, the crash dump save was started and completed.

Re: rx4640 mp log

whiteknight — Tue, 06 May 2008 05:00:41 GMT

Hi

Check if crashdump created in /var/adm/crash
you may need to analyse the crashdump

WK

Re: rx4640 mp log

Rasheed Tamton — Tue, 06 May 2008 06:44:50 GMT

Hi,

Sysem did a TOC (INIT in IPF) and crashdump.
Look for files in /var/adm/crash.

Also check, if there are any files in /var/tombstones

Regards.

Re: rx4640 mp log

JP Watson — Wed, 07 May 2008 14:45:24 GMT

Your system experienced a HPUX panic/crash. This is indicated by log entry 4068 where cpu 0 was the processor handleing the crash.

"OS legacy PA hex fault code (Bxxx). Possible I/O error or system panic
Logged by: HP-UX Kernel cabinet 0, slot 0, >>>cpu 0 <<<"

Log Entry 4057 shows that CPU 1 was "shutdown" by the crash monarch(cpu 0 in this case) by a INIT (or TOC). This is a normal process in the event of a Panic or MCA(Machine Check Abort).

Keyword: INIT_INITIATED
Logged by: System Firmware cabinet 0, slot 0, >>>cpu 1<<<<

There may be more information contained in MP/iLO logs, but your best course of action is to have the crash dump analyzed.

Depending on what is found, it may be necessary to gather the MCA data as well. This can be gathered from the efi shell with the command "errdump mca".