need help with N4000 GSP Log

[moonchild]

the system rebooted after a panic
ts99 is clean

any ideas?

attached is the GSP log

thanks in advance

[goldboy]

The GSP log does not specify any details for the reboot.
did you have any entry in the syslog file ?
also, was there a line created in the shutdownlog for this panic ?

this can be anything from a bad disk, processor to a PDC level problem.

Tal

[moonchild]

nothing in syslog or OLDSyslog.log

shutdownlog showed reboot after panic data page fault.

attached is the crashinfi outfut.

[goldboy]

Do you have a terminator interface installed accross from the PMB card (P/N A3639-60026) ?

Tal

[moonchild]

Yes a terminator is installed.

It panicked again with different messages:

shutdownlog:
03/02/07 around 6 PM
reboot after panic isr.ior=0.0.0

03/03/07 around 11:00 PM
reboot after panic : data memory protection fault.

oldsyslog is clean
exercising CPUs and memory came back with no errors

ts99 is clean no valid timestamp
stm logs are clean

PDC is the latest: 43.43

we were not able to get a full crashdump :(

recent GSP log is attached

thank you in advance for your help and input.

[moonchild]

The system oanicked again with:

Reboot After Panic isr.ior="0.0.0"

ts99 is clean

attached is the crashinfo output

Your help is much appreciated
Thanks in advance

[Sameer_Nirmal]

It looks like there is trap interruption 4 ( external interrupt) which couldn't be handled by HPUX. Thats why there is a protection fault reported.
Saying that the PANIC is on account software problem ( which is typical mostly). The Trap 4 was received by CPU 5 which made CPU 6,0 PANIC'ed and caused other CPUs TOCed. Now looking at the proc threads running on CPUs, the process "baseborg" comes into picture.
Do you know what this process is and what does it do?

Since there is no HPMC or trap 1 , there is no valid timestamp of HPMC in ts99. From GSP perspective, it is LPMC and shown as HPUX legacy chassis codes.