1753479 Members
4883 Online
108794 Solutions
New Discussion юеВ

Re: panic cpu:0

 
Joris Denayer
Respected Contributor

Re: panic cpu:0

OK,

I have to apoligize.
The mistery is solved. It's my fault.
This _panic_message changed with the installation of PatchKit #5.
Sorry for wasting entries

From Patchkit #5 onwards, the message changed to
"NULL fifo_bufhdr append pointer"

Joris

To err is human, but to really faul things up requires a computer
Michael Schulte zur Sur
Honored Contributor

Re: panic cpu:0

Hi Enrique,

how many members has your cluster? Have you had any troubles with the quorum disk lately?

greetings,

Michael
Michael Schulte zur Sur
Honored Contributor

Re: panic cpu:0

Hi Enrique,

you find this quite often in the crash file. I wonder, if the memory channel is damaged.

regards

Michael

rm_state_change: mchan0 slot 1 offline
rm_lrail_remove_node: logical_rail 0 hubslot 1
CNX MGR: communication error detected for node 2
CNX MGR: delay 1 secs 0 usecs
CNX QDISK: Cluster transition, releasing claim to 1 quorum disk vote.
CNX MGR: quorum lost, suspending cluster operations.
Joris Denayer
Respected Contributor

Re: panic cpu:0

Enrique,

~30 seconds before the crash, the other member went offline.
There are some known issues with clustermembers crashing, when an other member shutdown or powerdown.
Most of these issues are fixed in the patchkits.
Indeed, as Michael said, problems with the cluster interconnect will not help to make a cluster stable. Everything should be correct in terms of cabling, firwmware version, strapsetting, etc..
However, seen the uptime of the system, I believe more in a software problem.

Therefore, I should plan
1) the installation of the latest patchkit (kit#6)
or even better
2)an upgrade to v5.1B

This is only a free advise. If you want to know what happened exactly with your system and you have a valid contract then you can open a case at HP Services.

Joris
To err is human, but to really faul things up requires a computer
Michael Schulte zur Sur
Honored Contributor

Re: panic cpu:0

Hi Enrique,

are you stil with us?

greetings,

Michael
Enrique Carballido
Occasional Contributor

Re: panic cpu:0

I send more info.
Enrique Carballido
Occasional Contributor

Re: panic cpu:0

More info.
Joris Denayer
Respected Contributor

Re: panic cpu:0

Enrique,

The version of fifo_vnops.c is not the version delivered with patchkit#6.
I see that you installed patchkit #6, but it must have been installed only partially.
The vfs.mod which contains fifo_vnops.c is part of OSF510-1163
This is one of the most important patches (patch 1163). A lot of other patches depend on the installation of this one.
As it is not present in the patchlist, it must have been rejected during the run of dupatch.

I propose to run a dupatch baseline. This will give the reason why it is not installed.

Joris

To err is human, but to really faul things up requires a computer
Michael Schulte zur Sur
Honored Contributor

Re: panic cpu:0

Hi Enrique,

is the problem solved?

Michael