syslog SCSI:Request Timeout

Joseph Primm — Tue, 13 Jun 2000 18:21:29 GMT

I'm looking for information on how to interpret the following (how do I cross the dev: number and or determine which device is generating this, and is v11.0):

vmunix: SCSI: Request Timeout -- lbolt: 5166392, dev: 1f081100
vmunix: lbp->state: 4020
vmunix: lbp->offset: ffffffff
vmunix: lbp->uPhysScript: ffc17000
vmunix: From most recent interrupt:
vmunix: ISTAT: 22, SIST0: 04, SIST1: 00, DSTAT: 80, DSPS: 00000006
vmunix: lsp: 2ce0b00
vmunix: bp->b_dev: 1f081100
vmunix: scb->io_id: 81d34ae
vmunix: scb->cdb: 28 00 02 b9 d6 80 00 00 10 00
vmunix: lbolt_at_timeout: 5163292, lbolt_at_start: 5163292
vmunix: lsp->state: 10d
vmunix: lbp->owner: 2ce0b00
vmunix: scratch_lsp: 0
vmunix: Pre-DSP script dump [9fc17030]:
vmunix: 78346f00 0000000a 78350800 00000000
vmunix: 0e000004 ffc17500 e0100004 ffc1777c
vmunix: Script dump [9fc17050]:
vmunix: 9f0b0000 00000006 0a000000 ffc17508
vmunix: 721a0000 00000000 98080000 00000001
vmunix:
vmunix: SCSI: Abort Tag -- lbolt: 5166392, dev: 1f081100, io_id: 81d34ae

Re: syslog SCSI:Request Timeout

Brian M. Fisher — Tue, 13 Jun 2000 18:29:46 GMT

You can use the following information to determine which device
generates the lbolt/timeout errors:

1f 02 6 0 00
__ __ _ _ __
| | | | |
major# | target | flags
| |
bus# lun

Per this information:

- major# (1f) is 31 in decimal, and major number 31 should be
sdisk on your system.

- bus# (02) is the card instance number to which the device is
attached.

- target (6) is the device's scsi id.

- lun (0) is the device's logical unit number.

Therefore, this device maps to /dev/dsk/c2t6d0.

Brian
<*(((>< er

topic Re: syslog SCSI:Request Timeout in Operating System - HP-UX

syslog SCSI:Request Timeout

Re: syslog SCSI:Request Timeout