cancel
Showing results for 
Search instead for 
Did you mean: 

reboot after panic

Summery
Occasional Advisor

reboot after panic

I have the rp2470 server, OS is HPUX 11.11.
The warning lamp flashed red, and I found something wrong in /etc/shutdownlog like this:
Reboot after panic: , isr.ior = 0'40040.0'c8721db0

Could any one could help me ?
5 REPLIES
Ron Irving
Trusted Contributor

Re: reboot after panic

Hi.

If the system is up now, can you send the last few lines of the /var/adm/syslog/OLDsyslog.log.

Have a look at the mp logs for any clues.

Hope this helps!

Ron
Should have been an astronaut.
Rita C Workman
Honored Contributor

Re: reboot after panic

Not a whole lot of info...could be cause by hardware failure or even from application.

Not sure on rp2470, go into GSP or your MP port and read the console and/or event logs. This may help you begin ruling things out.

Another, if the box is back up...then look to /var/adm/crash and you could run Q4 on your crash [ SEARCH for Q4 for threads ]
or you might be able to run:
adb -m /var/adm/crash/crash_dir/vmunix /var/adm/crash/crash.0


Just a couple thoughts,
Rita

...remember you could SEARCH above for your error to find additional threads that may help you too...
Summery
Occasional Advisor

Re: reboot after panic

thanks for your help.
I send the log of GSP as below:
Log Entry # 0 :
SYSTEM NAME: uninitialized

DATE: 02/28/2010 TIME: 18:16:49

ALERT LEVEL: 3 = System blocked waiting for operator input


SOURCE: 1 = processor

SOURCE DETAIL: 1 = processor general SOURCE ID: 0

PROBLEM DETAIL: 0 = no problem detail


CALLER ACTIVITY: E = system warning STATUS: 0

CALLER SUBACTIVITY: F0 = implementation dependent

REPORTING ENTITY TYPE: E = HP-UX REPORTING ENTITY ID: 00


0xF8E000301100EF00 00000000 0000EF00 type 31 = legacy PA HEX chassis-code

0x58E008301100EF00 00006E01 1C121031 type 11 = Timestamp 02/28/2010 18:16:49

Type CR for next entry, Q CR to quit.



Log Entry # 1 :
SYSTEM NAME: uninitialized

DATE: 02/28/2010 TIME: 18:14:57

ALERT LEVEL: 3 = System blocked waiting for operator input


SOURCE: 1 = processor

SOURCE DETAIL: 1 = processor general SOURCE ID: 0

PROBLEM DETAIL: 0 = no problem detail


CALLER ACTIVITY: E = system warning STATUS: 0

CALLER SUBACTIVITY: 00 = implementation dependent

REPORTING ENTITY TYPE: E = HP-UX REPORTING ENTITY ID: 00


0xF8E000301100E000 00000000 0000E000 type 31 = legacy PA HEX chassis-code

0x58E008301100E000 00006E01 1C120E39 type 11 = Timestamp 02/28/2010 18:14:57

Type CR for next entry, - CR for previous entry, Q CR to quit.

The server is up now,but I want to know the reason of this situation.
Waiting for your help :)
Michael Steele_2
Honored Contributor

Re: reboot after panic

Hi

Still not enough for anything diffinitive.

Let's see some more:

/etc/shutdownlog (* what is the date of that entry - Does the 2/28 date from the SP match up? *)
/etc/opt/resmon/logs/*
/var/adm/syslog/OLDsyslog.log
/var/adm/crash

From the SP a processor is complaining, try entering FRU command from the BCH and attach report.

Regardless, you've got enough to call HP for a HW call to investigate the processor.
Support Fatherhood - Stop Family Law
Mike Miller_8
Regular Advisor

Re: reboot after panic

If the system is back up, check to see if you are missing one of the CPUs (System has 4 but only 3 show up on top). If this is the case - you probably have had a CPU die. Sometimes rebooting will clear this. If the CPU doesn't reset, replace it.