Date: Wed, 26 Mar 1997 11:43:36 -0700 From: "Justin T. Gibbs" <gibbs@plutotech.com> To: "Roy M. Hooper" <rhooper@toybox.ottawa.on.ca> Cc: gibbs@plutotech.com (Justin T. Gibbs), freebsd-scsi@FreeBSD.ORG Subject: Re: AHA2940 bug(s) still exist in 2.2.1 Message-ID: <199703261843.LAA27920@pluto.plutotech.com> In-Reply-To: Your message of "Wed, 26 Mar 1997 13:53:49 EST." <199703261853.NAA18416@toybox.ottawa.on.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
>> I need the exact timeout messages, information about what AHC options you >> have in your kernel config file, and the dmesg output listing the drives >> you are using. > >The exact timeout message is almost impossible to retreive as the system >tends to reboot and come back up 90% of the time. This normally happens >without us at the console - since the messages aren't logged to disk, we >never see them. One of the tech support guys saw the machine hung and >rebooted it for us this morning (without writing down the message). Can you hook up a serial console? >ahc0 <Adaptec 2940 SCSI host adapter> rev 3 int a irq 5 on pci0:17 >ahc0: aic7870 Single Channel, SCSI Id=7, 16 SCBs >ahc0 waiting for scsi devices to settle >(ahc0:0:0): "SEAGATE ST32151N 0284" type 0 fixed SCSI 2 >sd0(ahc0:0:0): Direct-Access 2049MB (4197405 512 byte sectors) >(ahc0:1:0): "SEAGATE ST32151N 0284" type 0 fixed SCSI 2 >sd1(ahc0:1:0): Direct-Access 2049MB (4197405 512 byte sectors) >(ahc0:2:0): "SEAGATE ST32151N 0284" type 0 fixed SCSI 2 >sd2(ahc0:2:0): Direct-Access 2049MB (4197405 512 byte sectors) >ahc1 <Adaptec 2940 Ultra SCSI host adapter> rev 0 int a irq 10 on pci0:18 >ahc1: aic7880 Single Channel, SCSI Id=7, 16 SCBs >ahc1 waiting for scsi devices to settle >(ahc1:0:0): "SEAGATE ST32151N 0284" type 0 fixed SCSI 2 >sd3(ahc1:0:0): Direct-Access 2049MB (4197405 512 byte sectors) >(ahc1:1:0): "SEAGATE ST32151N 0154" type 0 fixed SCSI 2 >sd4(ahc1:1:0): Direct-Access 2049MB (4197405 512 byte sectors) >(ahc1:2:0): "SEAGATE ST32430N 0510" type 0 fixed SCSI 2 >sd5(ahc1:2:0): Direct-Access 2049MB (4197405 512 byte sectors) Are these narrow or wide? I should be able to create a similar test setup sometime next week, if/when this motherboard I'm waiting on comes in. >There are no AHC options set. Then it's not the tagged queueing. I would have expected you to have at least AHC_TAGENABLE turned on in you config file. >> an Ordered Tagged transaction to the disk. This should force the drive to >> finish all pending transactions before starting any others. The current >> timeout for the Ordered Tagged transaction to be successful is only 1 >> second which perhaps isn't really long enough. Something that my help >> this problem is to perform ordered writes for all synch write operations >> which will be possible with the new SCSI code. > >Considering the Seagate Barracuda drives we have are rather fast, I would >guess that this is the problem. Not if you don't have the AHC_TAGENABLE option turned on. >1 second is rather short. Especially for something that may panic. It's not supposed to panic. It's supposed to start taking more drastic measures to restore order on the SCSI bus. That's why I want more acurate messages. >Wouldn't 5 seconds be a better timeout period? I already bumped it in my local version. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations ===========================================
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199703261843.LAA27920>