- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- HPE 9000 and HPE e3000 Servers
- >
- System hang detected via timer popping
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
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
Community
Resources
Forums
Blogs
- 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
05-17-2004 12:22 AM
05-17-2004 12:22 AM
System hang detected via timer popping
One of our cluster nodes (rp5470 2-CPU)suddenly went down with only the following message in the GSP (version B.02.14):
************* SYSTEM ALERT **************
SYSTEM NAME: krimson-gsp
DATE: 05/14/2004 TIME: 06:46:51
ALERT LEVEL: 13 = System hang detected via timer popping
REASON FOR ALERT
SOURCE: 1 = processor
SOURCE DETAIL: 1 = processor general SOURCE ID: 0
PROBLEM DETAIL: 4 = timeout
LEDs: RUN ATTENTION FAULT REMOTE POWER
OFF OFF OFF OFF FLASH
System Power is Off.
0x78E000D41100F000 00000003 00000001 - type 15 = Activity Level/Timeout
0x58E008D41100F000 00006804 0E062E33 - type 11 = Timestamp 05/14/2004 06:46:51
Let me be clear :
The system did not HANG, so a TOC is not an option to find more info.
The GSP comand "SS" returned with saying that System power was off. I could turn the system back on with the PC command, and after that it booted normally.
There is no entry in syslog.log, OLDsyslog.log or shutdownlog.
There are no other GSP messages just before the above GSP alert.
Since it happened (thursday may 20) it has not happened again and no new logs indicate any problem.
We are running a serviceguard cluster, but I don't believe that anythin in the cluster could cause the power to be switched off. It could halt, reboot or TOC a system, but not power-off (if I'm right).
Iam already in contact with HP support, but they don't seem to be able to lay their finger on the heart of the problem.
I know many of you have seen the same issue. Could you tell me what solvged this in your case ?
Regards, and many thanks in advance
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-17-2004 12:26 AM
05-17-2004 12:26 AM
Re: System hang detected via timer popping
I have only seen this when I've had a true hang on the box, but I suppose that you could "hang" long enough if you had a "mini-hang" that went for some time but then righted itself.
Something quick to check which is "uptime" on the box. Does this show that we really weren't down at this time (i.e. that we've been up longer then 4 days) ?
Nothing in shutdownlog doesn't mean the box didn't go down .. there are cases (especailly powerfails) that can reboot a box without a shutdownlog entry.
"uptime" on the other hand will tell us how long we've been running.
Best regards,
Kent M. Ostby
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-17-2004 12:37 AM
05-17-2004 12:37 AM
Re: System hang detected via timer popping
I think you misunderstood. The system went down. There is no discussion about that. If the power is off, I doubt that any system can keep running :-)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-17-2004 01:04 AM
05-17-2004 01:04 AM
Re: System hang detected via timer popping
Given what you have said, is there any data in the /var/tombstones/ts99 file ?
You can attempt to re-save a system crash by the following:
savecrash -r -v
where directory is the destination where you would like the crash to end up in.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-28-2005 08:35 PM
04-28-2005 08:35 PM
Re: System hang detected via timer popping
I too have an rp2470 with a single CPU which just hangs giving the similar "alert level 13" message.
The GSP f/w version i am using is C.02.14
Could you please tell me what was the solution to your problem?
Thanks,
Roopa
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-28-2005 08:52 PM
04-28-2005 08:52 PM
Re: System hang detected via timer popping
My system was a rp5470 and uses a different GSP firmware. Firmware version B.02.20 contained a fix for the symptoms we had on our server.
After the firmware upgrade of the GSP, the problem has not returned.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-28-2005 09:21 PM
04-28-2005 09:21 PM