- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- HPE 9000 and HPE e3000 Servers
- >
- the message from GSP's sl
HPE 9000 and HPE e3000 Servers
1753868
Members
7378
Online
108809
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
тАО11-22-2002 08:04 AM
тАО11-22-2002 08:04 AM
the message from GSP's sl
SYSTEM NAME: uninitialized
DATE: 25/10/2002 TIME: 10:43:04
ALERT LEVEL: 10 = Boot possible functionality lost
REASON FOR ALERT
SOURCE: 3 = PDH
SOURCE DETAIL: 6 = interconnect medium SOURCE ID: 0
PROBLEM DETAIL: 3 = non-responding may need GSP reset
CALL ACTIVITY :2=operation STATUS:0
CALL SUBACTIVITY STATUS:02 platform internal interconnect
REPORT ENTRY 1=service processor Reporting Entry ID :00
0x581008A336002020 00006609 190E2403 - type 11 = timestamp 25/10/2002
DATE: 25/10/2002 TIME: 10:43:04
ALERT LEVEL: 13 = sys hand detected via timer popping
REASON FOR ALERT
SOURCE: 1 = Processor
SOURCE DETAIL: 1 = proccessor general source id:0
PROBLEM DETAIL: 4 = timeout
CALL ACTIVITY F=display_activity() update
CALL SUBACTIVITY STATUS:00=implementation dependent
REPORT ENTRY E=HP-UX reporting Entry id:00
0x78E000041100F000 00000003 00000000 - type 15 = Activity level/Timeout
0x58E008D41100F000 00006609 190E2402 -type 11=Timestamp 10/25/2002
****************
According to above messages what problems with the systme ?
DATE: 25/10/2002 TIME: 10:43:04
ALERT LEVEL: 10 = Boot possible functionality lost
REASON FOR ALERT
SOURCE: 3 = PDH
SOURCE DETAIL: 6 = interconnect medium SOURCE ID: 0
PROBLEM DETAIL: 3 = non-responding may need GSP reset
CALL ACTIVITY :2=operation STATUS:0
CALL SUBACTIVITY STATUS:02 platform internal interconnect
REPORT ENTRY 1=service processor Reporting Entry ID :00
0x581008A336002020 00006609 190E2403 - type 11 = timestamp 25/10/2002
DATE: 25/10/2002 TIME: 10:43:04
ALERT LEVEL: 13 = sys hand detected via timer popping
REASON FOR ALERT
SOURCE: 1 = Processor
SOURCE DETAIL: 1 = proccessor general source id:0
PROBLEM DETAIL: 4 = timeout
CALL ACTIVITY F=display_activity() update
CALL SUBACTIVITY STATUS:00=implementation dependent
REPORT ENTRY E=HP-UX reporting Entry id:00
0x78E000041100F000 00000003 00000000 - type 15 = Activity level/Timeout
0x58E008D41100F000 00006609 190E2402 -type 11=Timestamp 10/25/2002
****************
According to above messages what problems with the systme ?
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-23-2002 01:51 AM
тАО11-23-2002 01:51 AM
Re: the message from GSP's sl
Hi Rambo,
Next link will give you a bit more info. I can't find a complete list of error codes.
http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x5784402f24d5d61190050090279cd0f9,00.html
Hope it helps.
Kind Regards,
Robert-Jan.
Next link will give you a bit more info. I can't find a complete list of error codes.
http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x5784402f24d5d61190050090279cd0f9,00.html
Hope it helps.
Kind Regards,
Robert-Jan.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-23-2002 03:53 AM
тАО11-23-2002 03:53 AM
Re: the message from GSP's sl
Rambo, if your system went down after these messages were displayed please call HP. Power monitor may need to be replaced
Please recall how many times and how often system does this way
Eugeny
Please recall how many times and how often system does this way
Eugeny
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-25-2002 02:10 AM
тАО11-25-2002 02:10 AM
Re: the message from GSP's sl
Rambo,
the mesage means that your GSP (Guardian Service Processor) is hanging. In fact it means that the I2C bus communication between system card and GSP failed. This may be a temporary overload of the I2C bus or a firmware hang of the GSP. This is normally an uncritical error which does not effect the running OS. I would recomend to reset the GSP and if this error happens freqeuntly, HP suppport should be contacted to perform a GSP firmware update if needed.
The GSP can be reset online (no problem for HPUX) by
a) pressing the GSP reset button on the Core I/O (only N-Class)
b) enter GSP mode (CTRL-b on the console) and entering "xd"
or c) from the OS by entering the command as root: "stty +resetGSP
Best regards
Stefan
the mesage means that your GSP (Guardian Service Processor) is hanging. In fact it means that the I2C bus communication between system card and GSP failed. This may be a temporary overload of the I2C bus or a firmware hang of the GSP. This is normally an uncritical error which does not effect the running OS. I would recomend to reset the GSP and if this error happens freqeuntly, HP suppport should be contacted to perform a GSP firmware update if needed.
The GSP can be reset online (no problem for HPUX) by
a) pressing the GSP reset button on the Core I/O (only N-Class)
b) enter GSP mode (CTRL-b on the console) and entering "xd"
or c) from the OS by entering the command as root: "stty +resetGSP
Best regards
Stefan
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