Well, here are the errors that came up:
Alert Level: 12 = Software Failure SOURCE: 0 = unknown, no source stated SOURCE ID: 0
Problem Detail = no problem detail
Caller Activity: B = System panic STATUS: 7
Reporting Entity type: E = HP-UX REPORTING ENTITY ID: 00
0xA0E000C00000B007 00000000 00000503 type 20 = major change in system state
0x58E008C00000B007 00007302 17151803 type 11 = Timestamp 3/23/2015 21:24:03
Date 01/01/1970
Alert Level: 10 = Boot possible, functionality lost
Source: 3 = PDH
Source Detail: 6 = interconnect medium SOURCE ID: 0
Problem Detail: 3 = nonresponding, may need GSP reset
Caller activity: 2 = operation STATUS: 0
Caller Subactivity: 02 platform internal interconnect
Reporting Entity Type: 1 = service processor
Reporting Entity ID: 00
Timstamp 01/01/1970 00::00:00
I guess there was more information there than I realized. Very strange that it lost the
current date and time on the second error. That second error occurs multiple times in
the log and is interspersed with older errors.
From: Craig Lalley [mailto:[log in to unmask]]
Sent: Tuesday, March 24, 2015 12:34 PM
To: Tom Hula; [log in to unmask]
Subject: Re: Sluggish/Frozen 3000
Control-B
SL (System Log) --> E (for Errors only)
Anything interesting?
CO puts you back in console mode.
-Craig
________________________________
From: Tom Hula <[log in to unmask]<mailto:[log in to unmask]>>
To: [log in to unmask]<mailto:[log in to unmask]>
Sent: Tuesday, March 24, 2015 6:54 AM
Subject: Sluggish/Frozen 3000
HP3000 Series A400/100/110 Version C.70.01
Our 3000 has been running fine for many years. Last night, there were fireworks of the wrong kind.
I was simply putting a tape on for the nightly backup. I noted that the load message never came up.
I then discovered that the console was frozen and unresponsive.
It has been a long time since the last reboot...since the last power outage. So I did a Ctrl-B and a reset.
It got up to the date and a little past and seemed frozen. I pulled the plug and restarted again. It took
2-3 times as long as normal and at first, the red fault light was on (never saw that on before). After
It got a bit into the restart, the fault light turned off by itself. The only attention message I got about
the whole thing was a message with everything unknown on it.
When the computer came all the way up, it still seemed very sluggish. I scheduled the nightly update
and backup and went home to look at it more in the morning. Logged on from home and the backup
seemed to be running OK.
This morning I tried resetting the GSP and checked the connections to the console terminal. I also found
out that someone else had a hard time getting on the 3000 towards the end of the day. Very sluggish.
This morning, everything seems back to normal. But I am concerned, since I don't know what the
problem was. It almost reminded me of something I used to call the Creeping Crud, where people
started freezing up all over the place, while some people were still able to work. The only thing was
a reboot. But in this case, it seemed worse. Only a few people on our 3000 now, but we still depend
on it for a high profile application.
Any suggestions on things I could check? Thanks!
Tom Hula
Victor S. Barnes Company
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
