panic cpu:0

[Enrique Carballido]

Hi,
I Had a problem that crash my Alpha/Tru64/Trucluster 5.1. This is the output from the UERF command. Does anyone knows what happened ? Can anyone help me ?
I can send more info, ...
Thanks for the help ...

********************************* ENTRY 7. *********************************

----- EVENT INFORMATION -----

EVENT CLASS ERROR EVENT
OS EVENT TYPE 110. MACHINE STATE
SEQUENCE NUMBER 0.
OPERATING SYSTEM DEC OSF/1
OCCURRED/LOGGED ON Thu Nov 13 18:57:54 2003
OCCURRED ON SYSTEM db1
SYSTEM ID x00080022
SYSTYPE x00000000
SYSTEM STATE x0003 CONFIGURATION

********************************* ENTRY 8. *********************************

----- EVENT INFORMATION -----

EVENT CLASS ERROR EVENT
OS EVENT TYPE 302. PANIC
SEQUENCE NUMBER 26418.
OPERATING SYSTEM DEC OSF/1
OCCURRED/LOGGED ON Thu Nov 13 18:53:59 2003
OCCURRED ON SYSTEM db1
SYSTEM ID x00080022
SYSTYPE x00000000
MESSAGE panic (cpu 0): What happened here ?

********************************* ENTRY 9. *********************************

----- EVENT INFORMATION -----

EVENT CLASS OPERATIONAL EVENT
OS EVENT TYPE 250. ASCII MSG
SEQUENCE NUMBER 26417.
OPERATING SYSTEM DEC OSF/1
OCCURRED/LOGGED ON Thu Nov 13 18:53:23 2003
OCCURRED ON SYSTEM db1
SYSTEM ID x00080022
SYSTYPE x00000000
MESSAGE mchan0: Node 1 is going offline

********************************* ENTRY 10. *********************************

[Joris Denayer]

Your system did a panic. With the provided information, we know nothing.

I don't know if this forum is the place for crash_analysis, but let's give it a try.

First the official way to handle this.
Run "sys_check -escalate".
Open a call at HP-services
On request, send the file escalate.tar and escalate.vmzcore to HP.

Second, we can have also have a short look at your crash.
So, send in attachment the most recent crash-data.* file from the directory /var/adm/crash.

This gives already an idea of what happened.
As the information in te crash_data file is limited, this is without garantuee



Rgrds


Joris

[Michael Schulte zur Sur]

Hi,

cd /var/adm/crash
see if you have a crash-data file and do
do a grep _panic_string crash-data.version and post it.

greetings,

Michael

[Joris Denayer]

Also interesting to know are the installed patchkits.
Post the output of following command.

# dupatch -track -type kit

Joris

[Ralf Puchner]

From the information given we know the panic string:

panic (cpu 0): What happened here ?

this indicates some kind of corruption or wrong parameter. But depend on the stack of the crash.

Please post you crash_data for further analysis.

[Joris Denayer]

Ralf,

I verified the sources of v5.1 and the TruCluster kernel routines.

The panicstring "What happened here" doesn't exist.

I think this is a comment of the original poster.

Joris

[Ralf Puchner]

Joris,

have a look to the entry 8. last sentence, this is not a comment it is well known panic string but the root cause needs further analysis.

[Joris Denayer]

Ralf,

Indeed. this is a panic_string in the v4 release stream (occurs in fifo_vnops.c)

But, it doesn't exist any longer in V5

The first post states we have Alpha/Tru64/Trucluster 5.1

Hmm.. this sounds interesting

Joris

[Enrique Carballido]

I send the crash file.

[Joris Denayer]

Enrique,

This is a tricky one. I do not understand this. I do not find the panic_string in the V5.1 sources. Is this system upgraded round 15 may 2003. This is the boottime before the crash.

Can you also send the output of
# dupatch -track -type kit
# dupatch -track -type patches
# sizer -v
# what /vmunix | grep fifo_vnops

Maybe this shed another light.

Joris