Skip site navigation (1)Skip section navigation (2)
Date:      17 Jul 2002 09:39:51 -0400
From:      Andrew Heybey <ath@niksun.com>
To:        Dave Hayes <dave@jetcafe.org>
Cc:        freebsd-scsi@FreeBSD.ORG
Subject:   Re: Random hangs on (at least) SCSI reads
Message-ID:  <858z4ajwwo.fsf@stiegl.mj.niksun.com>
In-Reply-To: <200207081851.g68Ipc069208@hokkshideh2.jetcafe.org>
References:  <200207081851.g68Ipc069208@hokkshideh2.jetcafe.org>

next in thread | previous in thread | raw e-mail | index | archive | help
> Note the following machine:
> FreeBSD dns.apolloi.com 4.5-RELEASE-p4
> ...
> ahc0: <Adaptec 29160 Ultra160 SCSI adapter> port 0xd800-0xd8ff mem 
> 0xff8ff000-0xff8fffff irq 10 at device 1.0 on pci1
> aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/255 SCBs
> ...
> ahc1: <Adaptec 29160 Ultra160 SCSI adapter> port 0xd400-0xd4ff mem 
> 0xff8fd000-0xff8fdfff irq 11 at device 3.0 on pci1
> aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/255 SCBs
> ...
> da0 at ahc0 bus 0 target 0 lun 0
> da0: <IBM IC35L036UWD210-0 S5BS> Fixed Direct Access SCSI-3 device 
> da0: 160.000MB/s transfers (80.000MHz, offset 63, 16bit), Tagged Queueing 
> Enabled
> da0: 35003MB (71687340 512 byte sectors: 64H 32S/T 35003C)
> da1 at ahc1 bus 0 target 0 lun 0
> da1: <IBM IC35L036UWD210-0 S5BS> Fixed Direct Access SCSI-3 device 
> da1: 160.000MB/s transfers (80.000MHz, offset 63, 16bit), Tagged Queueing 
> Enabled
> da1: 35003MB (71687340 512 byte sectors: 64H 32S/T 35003C)
> 
> I can consistently get this to hang (machine locks up, no panic or
> anything to console) on multiple machines with the exact same
> configuration by reading from the disk at high rates of speed
> (e.g. while (1) { find / -exec cat {} \; >/dev/null }). 
> 
> Anyone have any experience with this problem? Yes, I am working on
> upgrading it to 4.6-p1.

What motherboard?  Exactly how does it lock up?  Is there anything
else going on on the machine at the time?

I ask because we have seen hard lockups on an Intel STL2 motherboard.
A PCI bus analyzer on the bus sees the disk controller vainly trying
to do a memory read or write and being told to retry by the chipset.
We have seen these with 4.2 and with 4.5.

andrew

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-scsi" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?858z4ajwwo.fsf>