Subject: Re: scsi bus hangs on i386 running -current (28May97)
To: Jason Thorpe <thorpej@nas.nasa.gov>
From: Greg Wohletz <greg@duke.CS.UNLV.EDU>
List: current-users
Date: 05/31/1997 11:22:29
>Not really, no... here's my configuration:
>
>bha0 at pci0 dev 12 function 0: BusLogic 9xxC SCSI
>bha0: interrupting at irq 11
>bha0: model BT-958, firmware 5.05R
>bha0: sync, parity
>bha0 targ 0: sync, offset 15, period 100nsec
>bha0 targ 1: sync, offset 15, period 100nsec
>bha0 targ 8: sync, offset 15, period 100nsec
>scsibus0 at bha0: 16 targets
>sd0 at scsibus0 targ 0 lun 0: <SEAGATE, ST15230N, 0638> SCSI2 0/direct fixed
>sd0: 4095MB, 3992 cyl, 19 head, 110 sec, 512 bytes/sec
>sd1 at scsibus0 targ 1 lun 0: <SEAGATE, ST15230N, 0638> SCSI2 0/direct fixed
>sd1: 4095MB, 3992 cyl, 19 head, 110 sec, 512 bytes/sec
>sd2 at scsibus0 targ 8 lun 0: <SEAGATE, ST15230W, 0638> SCSI2 0/direct fixed
>sd2: 4095MB, 3992 cyl, 19 head, 110 sec, 512 bytes/sec
>
>dracul (thorpej) ~ 174% ccdconfig -g
>ccd0 64 0 /dev/sd0a /dev/sd1a
>
>I keep several source trees on the ccd, which are accessed by 5 or 6
>clients almost constantly, and the server itself does quite a bit
>of building. Objects are kept on sd2. Basically, this machine is
>my build server.
>
>What sort of activity is going on when you see the timeout problem?
It's a source tree also, I haven't been able to tie the hangs to any
particular activity, our hardware is:
bha0 at pci0 dev 20 function 0: BusLogic 9xxC SCSI
bha0: interrupting at irq 11
bha0: model BT-946C, firmware 4.28D
bha0: sync, parity
bha0 targ 0: sync, offset 15, period 100nsec
bha0 targ 1: sync, offset 15, period 100nsec
bha0 targ 2: sync, offset 15, period 100nsec
bha0 targ 3: sync, offset 15, period 100nsec
bha0 targ 5: sync, offset 15, period 100nsec
scsibus0 at bha0: 8 targets
sd0 at scsibus0 targ 0 lun 0: <SEAGATE, ST42100, 8224> SCSI2 0/direct fixed
sd0: 1812MB, 2574 cyl, 15 head, 96 sec, 512 bytes/sec
sd1 at scsibus0 targ 1 lun 0: <SEAGATE, ST42100, 8224> SCSI2 0/direct fixed
sd1: 1812MB, 2574 cyl, 15 head, 96 sec, 512 bytes/sec
sd2 at scsibus0 targ 2 lun 0: <SEAGATE, ST42100, 8224> SCSI2 0/direct fixed
sd2: 1812MB, 2574 cyl, 15 head, 96 sec, 512 bytes/sec
sd3 at scsibus0 targ 3 lun 0: <SEAGATE, ST42100, 8224> SCSI2 0/direct fixed
sd3: 1812MB, 2574 cyl, 15 head, 96 sec, 512 bytes/sec
st0 at scsibus0 targ 4 lun 0: <EXABYTE, EXB-8200, 2618> SCSI1 1/sequential removable
st0: drive empty
sd4 at scsibus0 targ 5 lun 0: <SEAGATE, ST42100, 8224> SCSI2 0/direct fixed
sd4: 1812MB, 2574 cyl, 15 head, 96 sec, 512 bytes/sec
ccd0 96 0 /dev/sd0e /dev/sd1e /dev/sd2e /dev/sd3e /dev/sd4e
Your configuration is so close I have a feeling this is a hardware issue on
my end. Maybe I need to investigate a firmware update on my controler.
--Greg