From: glh@dairynet.com
Date: Thu Mar 20 2003 - 10:25:32 EST
My debug skills on HP servers is very limited. We have a HP server that
essentially locks up and we can't free it without powering down the unit or
the external disk attached to it. Can anyone help me out on this, point me
in the right direction, offer any hints or tips? Thanks in advance.
Here's the last entry in /var/adm/syslog/syslog.log...
Mar 20 08:56:39 hpserv2 vmunix: SCSI: Request Timeout -- lbolt:
5865887, dev: 1f01f000
Here's what dmesg produces...
SCSI: Request Timeout -- lbolt: 5865887, dev: 1f01f000
lbp->state: 4020
lbp->offset: ffffffff
lbp->uPhysScript: 480000
From most recent interrupt:
ISTAT: 22, SIST0: 00, SIST1: 04, DSTAT: 00, DSPS: 00480500
lsp: 49aed80
bp->b_dev: 1f01f000
scb->io_id: 1052938
scb->cdb: 2a 00 00 00 2c 80 00 00 10 00
lbolt_at_timeout: 5862761, lbolt_at_start: 5862761
lsp->state: 10d
lbp->owner: 49aed80
scratch_lsp: 0
Pre-DSP script dump [49ff020]:
fbf48810 004807a4 410f0000 00480288
78347900 0000000a 78350800 00000000
Script dump [49ff040]:
0e000004 00480500 80000000 00000000
9f0b0000 00000006 0a000000 00480508
SCSI: Abort abandoned -- lbolt: 5865887, dev: 1f01f000, io_id: 1052938,
status: 200
SCSI: Request Timeout -- lbolt: 5866189, dev: 1f01f000
lbp->state: 4020
lbp->offset: ffffffff
lbp->uPhysScript: 480000
From most recent interrupt:
ISTAT: 22, SIST0: 00, SIST1: 04, DSTAT: 00, DSPS: 00480500
lsp: 481e800
bp->b_dev: 1f01f000
scb->io_id: 1052942
scb->cdb: 2a 00 00 00 2c d0 00 00 10 00
lbolt_at_timeout: 5863061, lbolt_at_start: 5863061
lsp->state: 10d
lbp->owner: 481e800
scratch_lsp: 0
Pre-DSP script dump [49ff020]:
fbf48810 00480790 410f0000 00480288
78347400 0000000a 78350800 00000000
Script dump [49ff040]:
0e000004 00480500 80000000 00000000
9f0b0000 00000006 0a000000 00480508
SCSI: Abort abandoned -- lbolt: 5866189, dev: 1f01f000, io_id: 1052942,
status: 200
DIAGNOSTIC SYSTEM WARNING:
The diagnostic logging facility has started receiving excessive
errors from the I/O subsystem. I/O error entries will be lost
until the cause of the excessive I/O logging is corrected.
If the diaglogd daemon is not active, use the Daemon Startup command
in stm to start it.
If the diaglogd daemon is active, use the logtool utility in stm
to determine which I/O subsystem is logging excessive errors.
LVM: vg[9]: pvnum=0 (dev_t=0x1f01f000) is POWERFAILED
--
---> Please post QUESTIONS and SUMMARIES only!! <---
To subscribe/unsubscribe to this list, contact majordomo@dutchworks.nl
Name: hpux-admin@dutchworks.nl Owner: owner-hpux-admin@dutchworks.nl
Archives: ftp.dutchworks.nl:/pub/digests/hpux-admin (FTP, browse only)
http://www.dutchworks.nl/htbin/hpsysadmin (Web, browse & search)
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 11:02:27 EDT