- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- HPE 9000 and HPE e3000 Servers
- >
- Re: A500 does not boot
HPE 9000 and HPE e3000 Servers
1752799
Members
5870
Online
108789
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-02-2004 04:07 AM
тАО09-02-2004 04:07 AM
A500 does not boot
can somone help here,
A500 machine, go down this night ath 00:53 with this GSP log.
Log Entry # 2 :
SYSTEM NAME: mispillgsp
DATE: 09/02/2004 TIME: 00:53:40
ALERT LEVEL: 12 = Software failure
SOURCE: 1 = processor
SOURCE DETAIL: 1 = processor general SOURCE ID: 0
PROBLEM DETAIL: 0 = no problem detail
CALLER ACTIVITY: B = system panic STATUS: 0
CALLER SUBACTIVITY: 00 = implementation dependent
REPORTING ENTITY TYPE: E = HP-UX REPORTING ENTITY ID: 00
0xA0E000C01100B000 00000000 000005E9 type 20 = major change in system state
0x58E008C01100B000 00006808 02003528 type 11 = Timestamp 09/02/2004 00:53:40
Log Entry # 3 :
SYSTEM NAME: mispillgsp
DATE: 09/02/2004 TIME: 00:53:40
ALERT LEVEL: 12 = Software failure
SOURCE: 1 = processor
SOURCE DETAIL: 1 = processor general SOURCE ID: 0
PROBLEM DETAIL: 0 = no problem detail
CALLER ACTIVITY: B = system panic STATUS: 0
CALLER SUBACTIVITY: 80 = implementation dependent
REPORTING ENTITY TYPE: E = HP-UX REPORTING ENTITY ID: 00
0xF8E000C01100B800 00000000 0000B800 type 31 = legacy PA HEX chassis-code
0x58E008C01100B800 00006808 02003528 type 11 = Timestamp 09/02/2004 00:53:40
Log Entry # 4 :
SYSTEM NAME: mispillgsp
DATE: 09/02/2004 TIME: 00:53:40
ALERT LEVEL: 12 = Software failure
SOURCE: 1 = processor
SOURCE DETAIL: 1 = processor general SOURCE ID: 0
PROBLEM DETAIL: 0 = no problem detail
CALLER ACTIVITY: B = system panic STATUS: 0
CALLER SUBACTIVITY: 00 = implementation dependent
REPORTING ENTITY TYPE: E = HP-UX REPORTING ENTITY ID: 00
0xA0E000C01100B000 00000000 000005E9 type 20 = major change in system state
0x58E008C01100B000 00006808 02003528 type 11 = Timestamp 09/02/2004 00:53:40
Log Entry # 5 :
SYSTEM NAME: mispillgsp
DATE: 09/02/2004 TIME: 00:53:40
ALERT LEVEL: 12 = Software failure
SOURCE: 1 = processor
SOURCE DETAIL: 1 = processor general SOURCE ID: 0
PROBLEM DETAIL: 0 = no problem detail
CALLER ACTIVITY: B = system panic STATUS: 0
CALLER SUBACTIVITY: 80 = implementation dependent
REPORTING ENTITY TYPE: E = HP-UX REPORTING ENTITY ID: 00
0xF8E000C01100B800 00000000 0000B800 type 31 = legacy PA HEX chassis-code
0x58E008C01100B800 00006808 02003528 type 11 = Timestamp 09/02/2004 00:53:40
restart this morning gave us this error
processor test 111B
processor test 111C
processor test 111D
processor cache test 2111
processor cache test 2112
processor cache test 2113
processor cache test 2121
processor cache test 2122
processor test 1151
unknown, no source stated machine check 0624
and this GSP LOG
Log Entry # 1 :
SYSTEM NAME: mispillgsp
DATE: 09/02/2004 TIME: 10:20:52
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: 00
0x0000002000FF6242 00000000 00000000 type 0 = Data Field Unused
0x5800082000FF6242 00006808 020A1434 type 11 = Timestamp 09/02/2004 10:20:52
what is wrong ???
A500 machine, go down this night ath 00:53 with this GSP log.
Log Entry # 2 :
SYSTEM NAME: mispillgsp
DATE: 09/02/2004 TIME: 00:53:40
ALERT LEVEL: 12 = Software failure
SOURCE: 1 = processor
SOURCE DETAIL: 1 = processor general SOURCE ID: 0
PROBLEM DETAIL: 0 = no problem detail
CALLER ACTIVITY: B = system panic STATUS: 0
CALLER SUBACTIVITY: 00 = implementation dependent
REPORTING ENTITY TYPE: E = HP-UX REPORTING ENTITY ID: 00
0xA0E000C01100B000 00000000 000005E9 type 20 = major change in system state
0x58E008C01100B000 00006808 02003528 type 11 = Timestamp 09/02/2004 00:53:40
Log Entry # 3 :
SYSTEM NAME: mispillgsp
DATE: 09/02/2004 TIME: 00:53:40
ALERT LEVEL: 12 = Software failure
SOURCE: 1 = processor
SOURCE DETAIL: 1 = processor general SOURCE ID: 0
PROBLEM DETAIL: 0 = no problem detail
CALLER ACTIVITY: B = system panic STATUS: 0
CALLER SUBACTIVITY: 80 = implementation dependent
REPORTING ENTITY TYPE: E = HP-UX REPORTING ENTITY ID: 00
0xF8E000C01100B800 00000000 0000B800 type 31 = legacy PA HEX chassis-code
0x58E008C01100B800 00006808 02003528 type 11 = Timestamp 09/02/2004 00:53:40
Log Entry # 4 :
SYSTEM NAME: mispillgsp
DATE: 09/02/2004 TIME: 00:53:40
ALERT LEVEL: 12 = Software failure
SOURCE: 1 = processor
SOURCE DETAIL: 1 = processor general SOURCE ID: 0
PROBLEM DETAIL: 0 = no problem detail
CALLER ACTIVITY: B = system panic STATUS: 0
CALLER SUBACTIVITY: 00 = implementation dependent
REPORTING ENTITY TYPE: E = HP-UX REPORTING ENTITY ID: 00
0xA0E000C01100B000 00000000 000005E9 type 20 = major change in system state
0x58E008C01100B000 00006808 02003528 type 11 = Timestamp 09/02/2004 00:53:40
Log Entry # 5 :
SYSTEM NAME: mispillgsp
DATE: 09/02/2004 TIME: 00:53:40
ALERT LEVEL: 12 = Software failure
SOURCE: 1 = processor
SOURCE DETAIL: 1 = processor general SOURCE ID: 0
PROBLEM DETAIL: 0 = no problem detail
CALLER ACTIVITY: B = system panic STATUS: 0
CALLER SUBACTIVITY: 80 = implementation dependent
REPORTING ENTITY TYPE: E = HP-UX REPORTING ENTITY ID: 00
0xF8E000C01100B800 00000000 0000B800 type 31 = legacy PA HEX chassis-code
0x58E008C01100B800 00006808 02003528 type 11 = Timestamp 09/02/2004 00:53:40
restart this morning gave us this error
processor test 111B
processor test 111C
processor test 111D
processor cache test 2111
processor cache test 2112
processor cache test 2113
processor cache test 2121
processor cache test 2122
processor test 1151
unknown, no source stated machine check 0624
and this GSP LOG
Log Entry # 1 :
SYSTEM NAME: mispillgsp
DATE: 09/02/2004 TIME: 10:20:52
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: 00
0x0000002000FF6242 00000000 00000000 type 0 = Data Field Unused
0x5800082000FF6242 00006808 020A1434 type 11 = Timestamp 09/02/2004 10:20:52
what is wrong ???
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-02-2004 05:21 AM
тАО09-02-2004 05:21 AM
Re: A500 does not boot
HI,
Appears to me that this is a probable CPU failure. I'd log a call to the Response Center. They'll be able to determine whether it's a HW or SW failure. But my money would be on HW since it's not booting.
How many CPUs are in that A500?
Rgds,
Jeff
Appears to me that this is a probable CPU failure. I'd log a call to the Response Center. They'll be able to determine whether it's a HW or SW failure. But my money would be on HW since it's not booting.
How many CPUs are in that A500?
Rgds,
Jeff
PERSEVERANCE -- Remember, whatever does not kill you only makes you stronger!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-02-2004 05:33 AM
тАО09-02-2004 05:33 AM
Re: A500 does not boot
there is 1 cpu in this machine
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-02-2004 06:54 AM
тАО09-02-2004 06:54 AM
Re: A500 does not boot
Hence no boot.
Bad CPU is reinforced by the fact that the POST is failing in the middle of a processor test.
Think you'll need to replace it.
Rgds,
Jeff
Bad CPU is reinforced by the fact that the POST is failing in the middle of a processor test.
Think you'll need to replace it.
Rgds,
Jeff
PERSEVERANCE -- Remember, whatever does not kill you only makes you stronger!
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP