System Panic

[Neil Wilson_2]

Anyone have any ideas what the following information might relate to in ascertaining why rp8400 vpar crashed?

model 9000/800/S16K-A
mem size 0x4 00000000
panic crfree: freeing free credential struct
dumptime 1107960676 Wed Feb 9 14:51:16 GMT 2005
savetime 1107961611 Wed Feb 9 15:06:51 GMT 2005
release @(#) $Revision: vmunix: vw: -proj selectors: CUPI80_BL2000_1108
-c 'Vw for CUPI80_BL2000_1108 build' -- cupi80_bl2000_1108 'CUPI80_BL2000_1108' Wed Nov 8 19:24:56 PST 2000
$
Uncompressing /var/adm/crash/crash.0/image.1.1 ........... done
Uncompressing /var/adm/crash/crash.0/image.2.1 ........... done
Uncompressing /var/adm/crash/crash.0/image.2.6 ........... done
adb>msgbuf+8/s
msgbuf+8: dsk/dg01/applvol file system full (1 block extent)
msgcnt 3608 vxfs: mesg 001: vx_nospace - /dev/vx/dsk/dg01/applvol file system fu
ll (1 block extent)
msgcnt 3610 vxfs: mesg 001: vx_nospace - /dev/vx/dsk/dg01/applvol file system fu
ll (1 block extent)
msgcnt 3612 vxfs: mesg 001: vx_nospace - /dev/vx/dsk/dg01/applvol file system fu
ll (1 block extent)
msgcnt 3614 vxfs: mesg 001: vx_nospace - /dev/vx/dsk/dg01/applvol file system fu
ll (1 block extent)
msgcnt 3616 vxfs: mesg 001: vx_nospace - /dev/vx/dsk/dg01/applvol file system fu
ll (1 block extent)
msgcnt 3618 vxfs: mesg 001: vx_nospace - /dev/vx/dsk/dg01/applvol file system fu
ll (1 block extent)
msgcnt 3620 vxfs: mesg 001: vx_nospace - /dev/vx/dsk/dg01/applvol file system fu
ll (1 block extent)
msgcnt 3622 vxfs: mesg 001: vx_nospace - /dev/vx/dsk/dg01/applvol file system fu
ll (1 block extent)
msgcnt 3624 vxfs: mesg 001: vx_nospace - /dev/vx/dsk/dg01/applvol file system fu
ll (1 block extent)
msgcnt 3626 vxfs: mesg 001: vx_nospace - /dev/vx/dsk/dg01/applvol file system fu
ll (1 block extent)
msgcnt 3628 vxfs: mesg 001: vx_nospace - /dev/vx/dsk/dg01/applvol file system fu
ll (1 block extent)
msgcnt 3630 vxfs: mesg 001: vx_nospace - /dev/vx/dsk/dg01/applvol file system fu
ll (1 block extent)
msgcnt 3632 vxfs: mesg 001: vx_nospace - /dev/vx/dsk/dg01/applvol file system fu
ll (1 block extent)
msgcnt 3634 vxfs: mesg 001: vx_nospace - /dev/vx/dsk/dg01/applvol file system fu
ll (1 block extent)
msgcnt 3636 vxfs: mesg 001: vx_nospace - /dev/vx/dsk/dg01/applvol file system fu
ll (1 block extent)
msgcnt 3638 vxfs: mesg 001: vx_nospace - /dev/vx/dsk/dg01/applvol file system fu
ll (1 block extent)
msgcnt 3640 vxfs: mesg 001: vx_nospace - /dev/vx/dsk/dg01/applvol file system fu
ll (1 block extent)
msgcnt 3642 vxfs: mesg 001: vx_nospace - /dev/vx/dsk/dg01/applvol file system fu
ll (1 block extent)
msgcnt 3644 vxfs: mesg 001: vx_nospace - /dev/vx/dsk/dg01/applvol file system fu
ll (1 block extent)
crfree(0x0000000060b01dc0) : bad cr_ref 0

[Scot Bean]

I would call HP, they can look at the image dumps collected in '/var/adm/crash/crash.0/' and hopefully tell you if this is a known problem, maybe there is already a patch for it.

[melvyn burnard]

looks like you have had a problem on a VxVM volume.
I suggest you log a call with your local HP Response Centre and have the crash dump analysed.

[A. Clay Stephenson]

I've seen this one in 11.0 but it was supposed to be fixed in 11.11. Yopu better call HP on this one.

http://www6.itrc.hp.com/service/cki/patchDocDisplay.do?patchId=equiv_data1100

and look for "crfree".