Operating System - HP-UX
1833723 Members
3894 Online
110063 Solutions
New Discussion

SCSI: First party detected bus hang

 
SOLVED
Go to solution
Stephanie L Davenport
Frequent Advisor

SCSI: First party detected bus hang

I'm getting the following error message and have not been able to figure it out. None of the disks are showing up as "NO_HW" but, my disk I/O is usually at 100% (in glance). I have used cstm to look at the arrays and it doesn't show anything wrong with the arrays.


Aug 27 23:37:14 hpbest vmunix:
Aug 27 23:37:14 hpbest vmunix: SCSI: First party detected bus hang -- lbolt: 286347277, bus: 0
Aug 27 23:37:14 hpbest vmunix: lbp->state: 1040
Aug 27 23:37:14 hpbest vmunix: lbp->offset: 10
Aug 27 23:37:14 hpbest vmunix: lbp->uPhysScript: 380000
Aug 27 23:37:14 hpbest vmunix: From most recent interrupt:
Aug 27 23:37:14 hpbest vmunix: ISTAT: 09, SIST0: 00, SIST1: 00, DSTAT: 84, DSPS: 00000002
Aug 27 23:37:14 hpbest vmunix: NCR chip register access history (most recent last): 580190673 accesses
Aug 27 23:37:14 hpbest vmunix: 2, SSTAT2: 00
Aug 27 23:37:14 hpbest vmunix: 2, SCNTL3: 1b
Aug 27 23:37:14 hpbest vmunix: 2, DSP<-00380148
Aug 27 23:37:14 hpbest vmunix: 17, ISTAT: 29
Aug 27 23:37:14 hpbest vmunix: 2, DSTAT: 84
Aug 27 23:37:14 hpbest vmunix: 2, DSPS: 00000001
Aug 27 23:37:14 hpbest vmunix: 2, SCRATCHA: ff0010a7
Aug 27 23:37:14 hpbest vmunix: 3, ISTAT<-00
Aug 27 23:37:14 hpbest vmunix: 2, DSP<-003804b0
Aug 27 23:37:14 hpbest vmunix: 2858, ISTAT: 09
Aug 27 23:37:14 hpbest vmunix: 2, DSTAT: 84
Aug 27 23:37:14 hpbest vmunix: 2, DSPS: 00000002
Aug 27 23:37:14 hpbest vmunix: 2, SCRATCHA: ff0010a7
Aug 27 23:37:14 hpbest vmunix: 3, DSP<-00380010
Aug 27 23:37:14 hpbest vmunix: 339, ISTAT<-20
Aug 27 23:37:14 hpbest vmunix: 4374114, ISTAT: 28
Aug 27 23:37:14 hpbest vmunix: lsp: 0
Aug 27 23:37:14 hpbest vmunix: lbp->owner: 5cc8200
Aug 27 23:37:14 hpbest vmunix: bp->b_dev: cb006002
Aug 27 23:37:14 hpbest vmunix: scb->io_id: a6c13f
Aug 27 23:37:14 hpbest vmunix: scb->cdb: 12 00 00 00 80 00
Aug 27 23:37:14 hpbest vmunix: lbolt_at_timeout: 286347182, lbolt_at_start: 286346682
Aug 27 23:37:14 hpbest vmunix: lsp->state: 5
Aug 27 23:37:14 hpbest vmunix: lsp->uPhysScript: 0
Aug 27 23:37:14 hpbest vmunix: lsp->upScript: 4926000
Aug 27 23:37:14 hpbest vmunix: lsp->upActivePtr: 4926000
Aug 27 23:37:14 hpbest vmunix: lsp->uActiveAdjust: 0
Aug 27 23:37:14 hpbest vmunix: lsp->upSavedPtr: 4926000
Aug 27 23:37:14 hpbest vmunix: lsp->uSavedAdjust: 0
Aug 27 23:37:14 hpbest vmunix: lsp->upPeakPtr: 4926000
Aug 27 23:37:14 hpbest vmunix: lsp->uPeakAdjust: 0
Aug 27 23:37:14 hpbest vmunix: scratch_lsp: 5cc8200
Aug 27 23:37:14 hpbest vmunix: Pre-DSP script dump [4935110]:
Aug 27 23:37:14 hpbest vmunix: 7834c000 00000000 78351000 00000000
Aug 27 23:37:14 hpbest vmunix: 78050800 00000000 78031b00 00000000
Aug 27 23:37:14 hpbest vmunix: Script dump [4935130]:
Aug 27 23:37:14 hpbest vmunix: 0e000005 00380700 80000000 00000000
Aug 27 23:37:14 hpbest vmunix: 9f0b0000 00000006 98080000 00000005
Aug 27 23:37:14 hpbest vmunix: NCR chip register dump:
Aug 27 23:37:14 hpbest vmunix: 00: SCNTL3: 1b SCNTL2: 80 SCNTL1: 10 SCNTL0: d8
Aug 27 23:37:14 hpbest vmunix: 04: GPREG: 07 SDID: 06 SXFER: 08 SCID: 47
Aug 27 23:37:14 hpbest vmunix: 08: SBCL: 2e SSID: 85 SOCL: 0e SFBR: 10
Aug 27 23:37:14 hpbest vmunix: 0c: SSTAT2: 00 SSTAT1: 0e SSTAT0: 20 DSTAT: 00
Aug 27 23:37:14 hpbest vmunix: 10: DSA: 00ff10ff
Aug 27 23:37:14 hpbest vmunix: 14: RESV14: ff RESV15: ff RESV16: ff ISTAT: 28
Aug 27 23:37:14 hpbest vmunix: 18: CTEST3: 40 CTEST2: 41 CTEST1: 60 CTEST0: 04
Aug 27 23:37:14 hpbest vmunix: 1c: TEMP: 004007a0
Aug 27 23:37:14 hpbest vmunix: 20: CTEST6: 03 CTEST5: 03 CTEST4: 88 DFIFO: 02
Aug 27 23:37:14 hpbest vmunix: 24: DCMDDBC: 0e000000
Aug 27 23:37:14 hpbest vmunix: 28: DNAD: 00380705
Aug 27 23:37:14 hpbest vmunix: 2c: DSP: 00380138
Aug 27 23:37:14 hpbest vmunix: 30: DSPS: 00380700
Aug 27 23:37:14 hpbest vmunix: 34: SCRATCHA: ff0010c0
Aug 27 23:37:14 hpbest vmunix: 38: DCNTL: 21 DWT: 00 DIEN: :
7f DMODE: 80
Aug 27 23:37:14 hpbest vmunix: 3c: ADDER: 00700838
Aug 27 23:37:14 hpbest vmunix: 40: SIST1: 00 SIST0: 40 SIEN1: 87 SIEN0: 8f
Aug 27 23:37:14 hpbest vmunix: 44: GPCNTL: 0f MACNTL: 00 SWIDE: ff SLPAR: b1
Aug 27 23:37:14 hpbest vmunix: 48: RESPID1: 00 RESPID0: 80 STIME1: 00 STIME0: 0c
Aug 27 23:37:14 hpbest vmunix: 4c: STEST3: 80 STEST2: 20 STEST1: 03 STEST0: 06
Aug 27 23:37:14 hpbest vmunix: 50: RESV50: ff RESV51: ff SIDL1: 00 SIDL0: 00
Aug 27 23:37:14 hpbest vmunix: 54: RESV54: ff RESV55: ff SODL1: ff SODL0: 02
Aug 27 23:37:14 hpbest vmunix: 58: RESV58: ff RESV59: ff SBDL1: 00 SBDL0: 02
Aug 27 23:37:14 hpbest vmunix: 5c: SCRATCHB: 320b7723
Aug 27 23:37:14 hpbest vmunix: Zalon register dump:
Aug 27 23:37:14 hpbest vmunix: IO_STATUS: f9000040
Aug 27 23:37:14 hpbest vmunix: IO_II_DATA: f9000040
Aug 27 23:37:14 hpbest vmunix: IO_DC_DATA: 51515151
Aug 27 23:37:23 hpbest vmunix:
Aug 27 23:37:23 hpbest vmunix: SCSI: Resetting SCSI -- lbolt: 286347377, bus: 0
Aug 27 23:37:23 hpbest vmunix:
Aug 27 23:37:23 hpbest vmunix: SCSI: Reset detected -- lbolt: 286347377, bus: 0
Aug 27 23:37:32 hpbest LVM[8128]: lvlnboot -v



sar -d 5 5 shows one of the disk arrays as follows:

Average c6t5d1 91.61 0.52 190 7852 4.68 12.57

Any ideas?
3 REPLIES 3
Sandman!
Honored Contributor
Solution

Re: SCSI: First party detected bus hang

Looks like you have a bad SCSI controller. Narrow it down by looking for the SCSI controller attached to "/dev/dsk/c0t6d0s2".

~hope it helps
Michael Steele_2
Honored Contributor

Re: SCSI: First party detected bus hang

Here is the complaining device: Aug 27 23:37:14 hpbest vmunix: bp->b_dev: cb006002

major number = cb or 203
controller = 00
target = 6
lun = 0
slice = 2

I get c0t6d0s2 for the culprit device name. And ioscan should confirm both the major number and device name appearing on the same line entry.

Regarding 'sar -d' report, cross reference with c0t6d0s2 and paste in.

Also check your /etc/opt/remons/log, /var/opt/resmon/log/event.log and STM > TOOLS > UTILITY > RUN > LOGTOOL > FILE > VIEW > RAW SUMMARY log.

Additionally, perform a 'll /dev/dsk' or 'll /dev/rmt' | grep 006002 is another way to id the problem device.

Support Fatherhood - Stop Family Law
Stephanie L Davenport
Frequent Advisor

Re: SCSI: First party detected bus hang

Darn it. I just realized that I've had to deal with this issue before. It's an unused internal drive that is causing this issue. Luckily, this system won't be up and running much longer. :)

Thanks for all your help!