Reboot after panic message

[Mark Hoensheid]

Good morning all...

I have a L2000 box running HPUX 11.1 and rebooted last night because of a panic message noted in the shutdown log.

01:11 Fri Jun 13 2003. Reboot after panic: , isr.ior = 0'a627ffe1.c0000000'edf86040
07:29 Wed Jul 16, 2003. Reboot: (by SAM)
07:30 Wed Jul 16, 2003. Reboot: (by cml2000!root)
16:17 Thu Aug 14, 2003. Halt: (by SAM)
16:18 Thu Aug 14, 2003. Halt: (by cml2000!root)
01:09 Tue Oct 28 2003. Reboot after panic: , isr.ior = 0'a627ffe1.c0000000'edf86000
14:46 Tue Nov 4, 2003. Halt: (by SAM)
14:46 Tue Nov 4, 2003. Halt:
14:09 Tue Nov 11, 2003. Reboot: (by SAM)
14:10 Tue Nov 11, 2003. Reboot: (by cml2000!root)
00:10 Thu Feb 05 2004. Reboot after panic: , isr.ior = 0'a627ffe1.c0000000'edf86040

This is very concerning since it resulting in a corrupt data file. Any ideas where to start troubleshooting this problem would be very helpful.

dmesg shows...

gate64: sysvec_vaddr = 0xc0002000 for 2 pages
NOTICE: autofs_link(): File system was registered at index 3.
NOTICE: cachefs_link(): File system was registered at index 5.
NOTICE: nfs3_link(): File system was registered at index 6.
0 sba
0/0 lba
0/0/0/0 btlan
0/0/1/0 c720
0/0/1/0.7 tgt
0/0/1/0.7.0 sctl
0/0/1/1 c720
0/0/1/1.0 tgt
0/0/1/1.0.0 sdisk
0/0/1/1.2 tgt
0/0/1/1.2.0 sdisk
0/0/1/1.7 tgt
0/0/1/1.7.0 sctl
0/0/2/0 c720
SCSI: First party detected bus hang -- lbolt: 3026, bus: 2
lbp->state: 7060
lbp->offset: 110
lbp->offset: 110
lbp->uPhysScript: f87ba000
From most recent interrupt:
ISTAT: 09, SIST0: 00, SIST1: 00, DSTAT: 84, DSPS: 0000000b
lsp: 0000000000000000
lbp->owner: 0000000040114c00
bp->b_dev: cb020002
scb->io_id: 2000001
scb->cdb: 12 00 00 00 80 00
lbolt_at_timeout: 2926, lbolt_at_start: 2426
lsp->state: 5
scratch_lsp: 0000000000000000
Pre-DSP script dump [fffffffff87ba068]:
98080000 00000001 e0100004 00000000
80000000 00000000 890b0000 f87ba198
Script dump [fffffffff87ba088]:
880b0000 f87ba198 83030000 f87ba368
0b000001 f87ba5d0 80040000 f87ba368
SCSI: Resetting SCSI -- lbolt: 3126, bus: 2
SCSI: Reset detected -- lbolt: 3126, bus: 2
System Console is on the Built-In Serial Interface
Entering cifs_init...
Initialization finished successfully... slot is 9
Logical volume 64, 0x3 configured as ROOT
Logical volume 64, 0x2 configured as SWAP
Logical volume 64, 0x2 configured as DUMP
Swap device table: (start & size given in 512-byte blocks)
entry 0 - major is 64, minor is 0x2; start = 0, size = 2097152
Dump device table: (start & size given in 1-Kbyte blocks)
entry 0000000000000000 - major is 31, minor is 0x12000; start = 314208, size = 1048576
Starting the STREAMS daemons-phase 1
Create STCP device files
$Revision: vmunix: vw: -proj selectors: CUPI80_BL2000_1108 -c 'Vw for CUPI80_BL2000_1108 build' -- cupi80_bl2000_1
108 'CUPI80_BL2000_1108' Wed Nov 8 19:24:56 PST 2000 $
Memory Information:
physical page size = 4096 bytes, logical page size = 4096 bytes
Physical: 1048576 Kbytes, lockable: 742880 Kbytes, available: 862344 Kbytes

Any help would be greatly appreciated and points will be awarded promptly.

Thanks in advance...

[Mark Grant]

It might be useful to look in

"/var/adm/syslog/OLDsyslog.log" to see if there is anythng suspicious before the machine fell over.

[melvyn burnard]

well this is either an HPMC (hardware problem usually), or a Serviceguard TOC, or a manually actuated TOC.
I would recpmmend you get the dump (should be in /var/adm/crash) analysed by your local HP Response Centre

[Jeff Schussele]

Hi,

You need to look for a couple of things:

1) A ts99 tombstone file in /var/adm/tombstones
2) A crash dump in /var/adm/crash

These will give more insight into cause. But looking at your msg, it's highly likely you had a HW induced panic.

Rgds,
Jeff

[Mark Hoensheid]

Thanks for the quick responses...

The OLDsyslog doesn't really show anything of importance related to hardware.

I have attached the ts99 file and it really means nothing to me since I can't read crash dumps.

[melvyn burnard]

You have had an HPMC.
I recommend you log a hardware call with your local HP Response Centre, supplying the ts99 file

[Paula J Frazer-Campbell]

Mark

It looks like a scsi problem

-SCSI: First party detected bus hang -- lbolt: 3026, bus: 2

Log a hardware call with HP.

Paula

[PVR]

Hi
check the following;
/var/adm/crash...... for a crash dump
/var/adm/tombstones/ts99
/var/adm/syslog/syslog.log
/var/adm/syslog/OLDsyslog.log

one more..

Login through console adn press ^B this will goto GSP. enter username and password
GSP>sl
then e
this will show the erros occurred last time.
Call a HP solution center and they will give you the details of problem, provided that you convey the exact HEX numbers appear on the last part of description