HPE 9000 and HPE e3000 Servers
cancel
Showing results for 
Search instead for 
Did you mean: 

HP 9000 N4000 GSP errors -- System crash---

 
Nour E Belkeir
Occasional Advisor

HP 9000 N4000 GSP errors -- System crash---

Hello,
I need some help with this error from GSP. I am on HP 11i V2 (11.23) PDC 43.43 and GSP A.01.12. I am not sure what firmware is needed to fix this problem or is there anything else I am overlooking. Can anybody help?

Thanks
nbelkeir@morehouse.edu

DATE: 07/27/2007 TIME: 01:54:26
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: 26 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 03

0x0000302000FF6262 00000000 00000000 type 0 = Data Field Unused
0x5800382000FF6262 00006B06 1B01361A type 11 = Timestamp 07/27/2007 01:54:26
Type CR for next entry, Q CR to quit.



Log Entry # 1 :
SYSTEM NAME: banhousegsp
DATE: 07/27/2007 TIME: 01:54:26
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: 03

0x0000302000FF6242 00000000 00000000 type 0 = Data Field Unused
0x5800382000FF6242 00006B06 1B01361A type 11 = Timestamp 07/27/2007 01:54:26
Type CR for next entry, - CR for previous entry, Q CR to quit.



Log Entry # 2 :
SYSTEM NAME: banhousegsp
DATE: 07/27/2007 TIME: 01:52:54
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: 25 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 04

0x0000402000FF6252 00000000 00000000 type 0 = Data Field Unused
0x5800482000FF6252 00006B06 1B013436 type 11 = Timestamp 07/27/2007 01:52:54
Type CR for next entry, - CR for previous entry, Q CR to quit.



Log Entry # 3 :
SYSTEM NAME: banhousegsp
DATE: 07/27/2007 TIME: 01:52:54
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: 04

0x0000402000FF6242 00000000 00000000 type 0 = Data Field Unused
0x5800482000FF6242 00006B06 1B013436 type 11 = Timestamp 07/27/2007 01:52:54
Type CR for next entry, - CR for previous entry, Q CR to quit.



Log Entry # 4 :
SYSTEM NAME: banhousegsp
DATE: 07/27/2007 TIME: 01:52:54
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: 25 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 07

0x0000702000FF6252 00000000 00000000 type 0 = Data Field Unused
0x5800782000FF6252 00006B06 1B013436 type 11 = Timestamp 07/27/2007 01:52:54
Type CR for next entry, - CR for previous entry, Q CR to quit.



Log Entry # 5 :
SYSTEM NAME: banhousegsp
DATE: 07/27/2007 TIME: 01:52:54
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: 07

0x0000702000FF6242 00000000 00000000 type 0 = Data Field Unused
0x5800782000FF6242 00006B06 1B013436 type 11 = Timestamp 07/27/2007 01:52:54
Type CR for next entry, - CR for previous entry, Q CR to quit.



Log Entry # 6 :
SYSTEM NAME: banhousegsp
DATE: 07/27/2007 TIME: 01:52:53
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: 04

0x0000402000FF6462 00000000 00000000 type 0 = Data Field Unused
0x5800482000FF6462 00006B06 1B013435 type 11 = Timestamp 07/27/2007 01:52:53
Type CR for next entry, - CR for previous entry, Q CR to quit.



Log Entry # 7 :
SYSTEM NAME: banhousegsp
DATE: 07/27/2007 TIME: 01:52:53
ALERT LEVEL: 2 = Non-Urgent operator attention required

SOURCE: 8 = I/O
SOURCE DETAIL: 2 = system bus adapter SOURCE ID: 1
PROBLEM DETAIL: 0 = no problem detail

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

0x7000402082016333 00000000 00B92200 type 14 = Problem Detail
0x5800482082016333 00006B06 1B013435 type 11 = Timestamp 07/27/2007 01:52:53
Type CR for next entry, - CR for previous entry, Q CR to quit.



Log Entry # 8 :
SYSTEM NAME: banhousegsp
DATE: 07/27/2007 TIME: 01:52:53
ALERT LEVEL: 2 = Non-Urgent operator attention required

SOURCE: 8 = I/O
SOURCE DETAIL: 2 = system bus adapter SOURCE ID: 0
PROBLEM DETAIL: 0 = no problem detail

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

0x7000402082006333 00000000 00B92200 type 14 = Problem Detail
0x5800482082006333 00006B06 1B013435 type 11 = Timestamp 07/27/2007 01:52:53
Type CR for next entry, - CR for previous entry, Q CR to quit.



Log Entry # 9 :
SYSTEM NAME: banhousegsp
DATE: 07/27/2007 TIME: 01:52:53
ALERT LEVEL: 2 = Non-Urgent operator attention required

SOURCE: 7 = memory
SOURCE DETAIL: 0 = unknown, no source stated SOURCE ID: 1
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: 04

0x7000402070016082 00000000 00992600 type 14 = Problem Detail
0x5800482070016082 00006B06 1B013435 type 11 = Timestamp 07/27/2007 01:52:53
Type CR for next entry, - CR for previous entry, Q CR to quit.



Log Entry # 10 :
SYSTEM NAME: banhousegsp
DATE: 07/27/2007 TIME: 01:52:53
ALERT LEVEL: 2 = Non-Urgent operator attention required

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

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

0x6000402070016072 00000000 00080800 type 12 = Device Status
0x5800482070016072 00006B06 1B013435 type 11 = Timestamp 07/27/2007 01:52:53
Type CR for next entry, - CR for previous entry, Q CR to quit.



Log Entry # 11 :
SYSTEM NAME: banhousegsp
DATE: 07/27/2007 TIME: 01:52:53
ALERT LEVEL: 2 = Non-Urgent operator attention required

SOURCE: 7 = memory
SOURCE DETAIL: 0 = unknown, no source stated SOURCE ID: 1
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: 04

0x6000402070016062 00000000 00080800 type 12 = Device Status
0x5800482070016062 00006B06 1B013435 type 11 = Timestamp 07/27/2007 01:52:53
Type CR for next entry, - CR for previous entry, Q CR to quit.



Log Entry # 12 :
SYSTEM NAME: banhousegsp
DATE: 07/27/2007 TIME: 01:52:53
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: 07

0x0000702000FF6462 00000000 00000000 type 0 = Data Field Unused
0x5800782000FF6462 00006B06 1B013435 type 11 = Timestamp 07/27/2007 01:52:53
Type CR for next entry, - CR for previous entry, Q CR to quit.



Log Entry # 13 :
SYSTEM NAME: banhousegsp
DATE: 07/27/2007 TIME: 01:52:53
ALERT LEVEL: 2 = Non-Urgent operator attention required

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

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

0x1800702011076322 CBA18000 00000000 type 3 = Actual Data
0x5800782011076322 00006B06 1B013435 type 11 = Timestamp 07/27/2007 01:52:53
Type CR for next entry, - CR for previous entry, Q CR to quit.



Log Entry # 14 :
SYSTEM NAME: banhousegsp
DATE: 07/27/2007 TIME: 01:52:53
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: 04

0x7000402070006082 00000000 009A2600 type 14 = Problem Detail
0x5800482070006082 00006B06 1B013435 type 11 = Timestamp 07/27/2007 01:52:53
Type CR for next entry, - CR for previous entry, Q CR to quit.



Log Entry # 15 :
SYSTEM NAME: banhousegsp
DATE: 07/27/2007 TIME: 01:52:53
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: 28 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 07

0x0000702000FF6282 00000000 00000000 type 0 = Data Field Unused
0x5800782000FF6282 00006B06 1B013435 type 11 = Timestamp 07/27/2007 01:52:53
Type CR for next entry, - CR for previous entry, Q CR to quit.
3 REPLIES 3
tkc
Esteemed Contributor

Re: HP 9000 N4000 GSP errors -- System crash---

The GSP log gave 'CALLER ACTIVITY: 6 = machine check'. It means your system has been rebooted due to a possible hard error. If the server is able to be booted up to the O/S after that, you have to collect the ts99 file in /var/tombstones directory to get it analysed for the root cause.
Peter Fecko
Occasional Advisor

Re: HP 9000 N4000 GSP errors -- System crash---

Hello, please what was the problem? Have you found the solution? We have now the same problem on N4000. Thank you.
Torsten.
Acclaimed Contributor

Re: HP 9000 N4000 GSP errors -- System crash---

SOURCE: 8 = I/O
SOURCE DETAIL: 2 = system bus adapter SOURCE ID: 1


This looks to me like the reason for trouble. Could be a bad I/O backplane, bad systemboard, bad core I/O or even bad PCI card. More info would be needed.

@Peter:
Consider to contact HP support and/or open your own thread!

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!