Reboot after panic

[Filosofo]

Hi All,
I have an hpux 11i, yesterday we change maxvgs kernel parameters from 10 to 200 and ntpy from 64 to 200....I make this chenge on another UGUAL machine and I havent problem.
When I clik on reboot the system from SAM, the server go SHUTDOWN IMMEDIATLY and correct....but when I try to connect the System Console I see the was panic...Why?
In etc/shutdownlog there is write:
19:46 Tue Jul 29 2003. Reboot after panic: , isr.ior = 0'240003.0'b12c5ee0

and in OLDsyslog I find
syslogd: going down on signal 15

What is the cause of the panic...

please help me

Filosofo

[Tom Geudens]

Hi,
There should be a dumpdirectory underneath /var/adm/crash (probably crash.1). This will contain the information HP needs to deduce what went wrong ...
You may also look at /var/tombstones ... the most recent file there might give information on the problem.

Regards,
Tom Geudens

[twang]

Do you check the shutdownlog, if it recorded a panic, then it may be a O/S problem.
Do you check the /var/tomstones, it usually record HW problem.
And you must have a look at your patches.

[melvyn burnard]

Is this system perhaps part of a ServiecGuard cluster?
If so, by rebuilding the kernel and then saying "reboot", this causes process to be sent a kill -9 signal.
If the cmcld process gets this, then it dies (obviously) and the Safety Timer kicks in, resulting in a ServiceGuard TOC.

[sdip]

It would be better if you recompile kernel again. Probably recompiling kernel process got terminated by any unwanted signal. Try to recompile again and reboot the server.

[twang]

Since the panic shows an "isr.ior" error,
It seems that you had a HW problem, you may have to verify entries in /var/tombstones.ts99 for any indication. If so, you need to contact HP support and they may need to have a look at the contents of tombstone.