rp5470 error log decode

[Steve Boniwell]

My customer has had an unscheduled reboot on his rp5470. The last messsage in the log is :

Log Entry # 0:
SYSTEM NAME: uninitialized
DATE: 03/25/2007 TIME: 00:00:30
ALERT LEVEL: 13 = System hang detected via timer popping

SOURCE: 6 = platform
SOURCE DETAIL: 7 = power monitor SOURCE ID: 0
PROBLEM DETAIL: 4 = internal failure

CALLER ACTIVITY: 1 = initialization STATUS: F
CALLER SUBACTIVITY: 01 = self
REPORTING ENTITY TYPE: 2 = power monitor REPORTING ENTITY ID: 00

0x002000D46700101F 00000000 00000000 type 0 = Data Field Unused
0x582008D46700101F 00006B02 1900001E type 11 = Timestamp 03/25/2007
00:00:30

Log Entry #1
SYSTEM NAME: uninitialized
DATE: 03/25/2007 TIME 00:00:23
ALERT LEVEL: 2 = Non-Urgent operator attention required

SOURCE: 3 = PDH
SOURCE DETAIL: 6 = interconnect medium SOURCE ID: 0
PROBLEM DETAIL: 3 = non-responding, may need GSP reset

CALLER ACTIVITY: 2 = operation STATUS: 0
CALLER SUBACTIVITY: 02 = platform internal interconnect
REPORTING ENTITY TYPE: 1 = service processor REPORTING ENTITY ID: 00

0x5810082336002020 00006B02 19000017 type 11 = Timestamp 03/25/2007

Does this signify a faulty power supply or is their some other reading?

TIA Steve

[Joshua Scott · Accepted solution]

The 'System hang detected via timer popping' message may indicate a kernel panic or a failing CPU.

The second log looks like you need to reset the GSP. usually this is done by going into the GSP and running the XD command and selecting the appropriate option.

Make sure you are on the latest firmware revisions, as these crashes may be caused by older firmware.

Josh

[Andrew Rutter]

hi steve,

I agree with joshua, these are usually down to a bug in older firmware version for the GSP.

Check which version is installed by logging into the gsp and typing he
GSP>he

This will list the current installed version and whether it is an A version or B version.

Andy

[Andrew Rutter]

steve,

to add further to my last post, this is an exert from the patch details for the GSP b Version update

Another possible chassis code "footprint" would be this Alert Level 13 Error:
Log Entry # 5 :
SYSTEM NAME: HP000001
DATE: 12/15/2002 TIME: 06:06:48
ALERT LEVEL: 13 = System hang detected via timer popping

SOURCE: 6 = platform
SOURCE DETAIL: 7 = power monitor SOURCE ID: 0
PROBLEM DETAIL: 4 = internal failure

CALLER ACTIVITY: 1 = initialization STATUS: F
CALLER SUBACTIVITY: 01 = self
REPORTING ENTITY TYPE: 2 = power monitor ID: 00

0x002000D46700101F 00000000 00000000
0x582008D46700101F 00006608 0F060630
There may or may not always be an Alert Level 13 event logged and in those cases the only typical indication of the reboot condition will typically be the Alert Level 1 "System stage change: Booting" logged by "system firmware" as is shown in log event #1 above.

This is available from here and is version B.02.21


http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=15351&prodSeriesId=2512037&swItem=pf-41402-1&prodNameId=86772&swEnvOID=7&swLang=13&taskId=135&mode=4&idx=1

Andy