A500 sudden hang

[Sam_88]

I got a problem which is a A500 system sudden hang up. I had capture some GSP code. Anyone can help me about this? Thanks!!

The first entry is the most recent Chassis Code
Type + CR and CR to go up (back in time),
Type - CR and CR to go down (forward in time),
Type Q/q CR to quit.


Log Entry # 0 :
SYSTEM NAME: uninitialized
DATE: 06/12/2004 TIME: 15:18:29
ALERT LEVEL: 2 = Non-Urgent operator attention required

SOURCE: 0 = unknown, no source stated
SOURCE DETAIL: 0 = unknown, no source stated SOURCE ID: FF
PROBLEM DETAIL: 0 = no problem detail

CALLER ACTIVITY: 6 = machine check STATUS: 2
CALLER SUBACTIVITY: 46 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 01

0x0000102000FF6462 00000000 00000000 type 0 = Data Field Unused
0x5800182000FF6462 00006805 0C0F121D type 11 = Timestamp 06/12/2004 15:18:29
Type CR for next entry, Q CR to quit.



Log Entry # 1 :
SYSTEM NAME: uninitialized
DATE: 06/12/2004 TIME: 15:18:29
ALERT LEVEL: 2 = Non-Urgent operator attention required

SOURCE: 7 = memory
SOURCE DETAIL: 9 = unexpected SOURCE ID: 0
PROBLEM DETAIL: 3 = unexpected

CALLER ACTIVITY: 6 = machine check STATUS: 3
CALLER SUBACTIVITY: 13 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 01

0x7000102379006133 C1BFF0FF FED08040 type 14 = Problem Detail
0x5800182379006133 00006805 0C0F121D type 11 = Timestamp 06/12/2004 15:18:29
Type CR for next entry, - CR for previous entry, Q CR to quit.



Log Entry # 2 :
SYSTEM NAME: uninitialized
DATE: 06/12/2004 TIME: 15:18:29
ALERT LEVEL: 2 = Non-Urgent operator attention required

SOURCE: 7 = memory
SOURCE DETAIL: 0 = unknown, no source stated SOURCE ID: 0
PROBLEM DETAIL: 0 = no problem detail

CALLER ACTIVITY: 6 = machine check STATUS: 2
CALLER SUBACTIVITY: 08 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 01

0x7000102070006082 00000000 00B92400 type 14 = Problem Detail
0x5800182070006082 00006805 0C0F121D type 11 = Timestamp 06/12/2004 15:18:29
Type CR for next entry, - CR for previous entry, Q CR to quit.



Log Entry # 3 :
SYSTEM NAME: uninitialized
DATE: 06/12/2004 TIME: 15:18:29
ALERT LEVEL: 2 = Non-Urgent operator attention required

SOURCE: 7 = memory
SOURCE DETAIL: 0 = unknown, no source stated SOURCE ID: 0
PROBLEM DETAIL: 0 = no problem detail

CALLER ACTIVITY: 6 = machine check STATUS: 2
CALLER SUBACTIVITY: 06 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 01

0x6000102070006062 00000000 00100010 type 12 = Device Status
0x5800182070006062 00006805 0C0F121D type 11 = Timestamp 06/12/2004 15:18:29
Type CR for next entry, - CR for previous entry, Q CR to quit.



Log Entry # 4 :
SYSTEM NAME: uninitialized
DATE: 06/12/2004 TIME: 15:18:29
ALERT LEVEL: 7 = reserved

SOURCE: 0 = unknown, no source stated
SOURCE DETAIL: 0 = unknown, no source stated SOURCE ID: FF
PROBLEM DETAIL: 0 = no problem detail

CALLER ACTIVITY: 6 = machine check STATUS: 2
CALLER SUBACTIVITY: 29 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 01

0x0000107000FF6292 00000000 7F9AB000 type 0 = Data Field Unused
0x5800187000FF6292 00006805 0C0F121D type 11 = Timestamp 06/12/2004 15:18:29
Type CR for next entry, - CR for previous entry, Q CR to quit.



Log Entry # 5 :
SYSTEM NAME: uninitialized
DATE: 06/12/2004 TIME: 15:18:29
ALERT LEVEL: 2 = Non-Urgent operator attention required

SOURCE: 1 = processor
SOURCE DETAIL: 1 = processor general SOURCE ID: 1
PROBLEM DETAIL: 0 = no problem detail

CALLER ACTIVITY: 6 = machine check STATUS: 2
CALLER SUBACTIVITY: 35 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 01

0x1800102011016352 CB858000 00000000 type 3 = Actual Data
0x5800182011016352 00006805 0C0F121D type 11 = Timestamp 06/12/2004 15:18:29
Type CR for next entry, - CR for previous entry, Q CR to quit.



Log Entry # 6 :
SYSTEM NAME: uninitialized
DATE: 06/12/2004 TIME: 15:18:29
ALERT LEVEL: 2 = Non-Urgent operator attention required

SOURCE: 0 = unknown, no source stated
SOURCE DETAIL: 0 = unknown, no source stated SOURCE ID: FF
PROBLEM DETAIL: 0 = no problem detail

CALLER ACTIVITY: 6 = machine check STATUS: 2
CALLER SUBACTIVITY: 24 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 01

0x0000102000FF6242 00000000 00000000 type 0 = Data Field Unused
0x5800182000FF6242 00006805 0C0F121D type 11 = Timestamp 06/12/2004 15:18:29
Type CR for next entry, - CR for previous entry, Q CR to quit.



Log Entry # 7 :
SYSTEM NAME: uninitialized
DATE: 06/12/2004 TIME: 15:18:28
ALERT LEVEL: 2 = Non-Urgent operator attention required

SOURCE: 0 = unknown, no source stated
SOURCE DETAIL: 0 = unknown, no source stated SOURCE ID: FF
PROBLEM DETAIL: 0 = no problem detail

CALLER ACTIVITY: 6 = machine check STATUS: 2
CALLER SUBACTIVITY: 10 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 00

0x0000002000FF6102 00000000 00000000 type 0 = Data Field Unused
0x5800082000FF6102 00006805 0C0F121C type 11 = Timestamp 06/12/2004 15:18:28
Type CR for next entry, - CR for previous entry, Q CR to quit.


Regards,
Sam

[Shaikh Imran]

Hi,
There seem to be no problem with the server hardware or O.S.
As per the syslog attached the server was issued a command :
Jun 14 11:07:14 shkodb01 CM-CMD[18396]: /usr/sbin/cmhaltnode -vf
Probably by the user admin9-root
Have you by mistake given this or there was a purpose of doing so.

Please see the attached syslogcase.doc file in word format where it's highlighted.

Pls revert back after doing so.

Regards

[Sam_88]

Hi, Shaikh Imran
Thanks for your advise. Yes, I am going to stop one of the package of MC/SG and free the concole port to check the status of the A500 server. As I am using the console port as the heartbeat instead. However, I am fresh on problem handling. From the GSP capturing, I saw there is some kinds of fault about the CPU and memory. Is there anything which is related to? Please suggest some ideas to check on the machine. I don't have any HP support on this system. And before I ask my boss to pay for it. Thanks!!

[Jim Thomas_5]

Sam,
These GSP entries are indicitive of an HPMC on this system. To really understand the root cause of this HPMC you would have to get an HP CPU H/W specialist to read the HPMC PIM data that was stored in the /var/tombstones file or can be gathered at the BCH Service "PIM HPMC" command level. If you find you can create this HPMC "on demand" then the root problem might have software problems at its base. Sometimes a Core File analysis will help point to the S/W problem causing this HPMC.

[Shaikh Imran]

Hi,
Are you able to boot properly after acknowlwding the aboe gsp logs ?
If yes have you done a clean shutdown and see if you are getting into the same logs menu or are able to get into the system properly.
Also please check the syslog for any other error messages once you get into the system.

As you are near the system i will leave it to yourself to decode the GSP codes.

Pls follow this link to get the GSP codes info:
http://web.tampabay.rr.com/batcave/GSPinfo.htm#HELP_ON_ADMIN

Regards,