AIC7xxx timeouts in 2.1.125 and .126pre2

Ben Gertzfield (che@debian.org)
20 Oct 1998 19:02:01 -0700


After upgrading from 2.1.123 to 2.1.125, I began to have a very large
number of timeout errors and SCSI bus resets from the AIC7xxx driver.

My card is using the AHA-294X Ultra SCSI support, and works in
2.1.123 (version 5.0.20/3.2.4 of the driver) but as soon as I
boot into 2.1.125 (5.1.0/3.2.4) I get timeouts all over the place.

Rebooting with aic7xxx=verbose, I get these errors:

Ultra SCSI host adapter> found at PCI 16/0
(scsi0) Wide Channel, SCSI ID=7, 16/255 SCBs
(scsi0) Warning - detected auto-termination
(scsi0) Please verify driver detected settings are correct.
(scsi0) If not, then please properly set the device termination
(scsi0) in the Adaptec SCSI BIOS by hitting CTRL-A when prompted
(scsi0) during machine bootup.
(scsi0) Cables present (Int-50 YES, Int-68 YES, Ext-68 NO)
(scsi0) Downloading sequencer code... 419 instructions downloaded
scsi0 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 5.1.0/3.2.4
<Adaptec AHA-294X Ultra SCSI host adapter>
scsi : 1 host.
scsi : aborting command due to timeout : pid 0, scsi0, channel 0, id 0, lun 0 0x
00 00 00 00 00 00
(scsi0:0:0:0) Aborting scb 14, flags 0xc
(scsi0:0:0:0) SCB is currently active. Waiting on completion.
SCSI host 0 abort (pid 0) timed out - resetting
SCSI bus is being reset for host 0 channel 0.
(scsi0:0:0:0) Reset called, scb 14, flags 0x8c
(scsi0:0:0:0) Bus device reset stupid when other action has failed.
(scsi0:0:-1:-1) Reset channel called, will initiate reset.
(scsi0:0:-1:-1) Resetting currently active channel.
(scsi0:0:-1:-1) Reset device, active_scb 0
(scsi0:0:0:-1) Cleaning up status information and delayed_scbs.
(scsi0:0:1:-1) Cleaning up status information and delayed_scbs.
(scsi0:0:2:-1) Cleaning up status information and delayed_scbs.
(scsi0:0:3:-1) Cleaning up status information and delayed_scbs.
(scsi0:0:4:-1) Cleaning up status information and delayed_scbs.
(scsi0:0:5:-1) Cleaning up status information and delayed_scbs.
(scsi0:0:6:-1) Cleaning up status information and delayed_scbs.
(scsi0:0:7:-1) Cleaning up status information and delayed_scbs.
(scsi0:0:8:-1) Cleaning up status information and delayed_scbs.
(scsi0:0:9:-1) Cleaning up status information and delayed_scbs.
(scsi0:0:10:-1) Cleaning up status information and delayed_scbs.
(scsi0:0:11:-1) Cleaning up status information and delayed_scbs.
(scsi0:0:12:-1) Cleaning up status information and delayed_scbs.
(scsi0:0:13:-1) Cleaning up status information and delayed_scbs.
(scsi0:0:14:-1) Cleaning up status information and delayed_scbs.
(scsi0:0:15:-1) Cleaning up status information and delayed_scbs.
(scsi0:0:-1:-1) Cleaning QINFIFO.
(scsi0:0:-1:-1) Cleaning waiting_scbs.
(scsi0:0:-1:-1) Cleaning waiting for selection list.
(scsi0:0:-1:-1) Cleaning disconnected scbs list.
(scsi0:0:0:0:tag14) matches search criteria (scsi0:0:-1:-1:tag255)
(scsi0:0:0:0:tag14) matches search criteria (scsi0:0:-1:-1:tag255)
(scsi0:0:-1:-1) Channel reset
(scsi0:0:0:0) Aborting scb 14
(scsi0:-1:-1:-1) 1 commands found and queued for completion.
Vendor: IBM Model: DDRS-39130W Rev: S71D
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sda at scsi0, channel 0, id 0, lun 0
Vendor: YAMAHA Model: CRW4260 Rev: 1.0f
Type: CD-ROM ANSI SCSI revision: 02
Detected scsi CD-ROM sr0 at scsi0, channel 0, id 1, lun 0

The system does continue to boot, but it blocks for about 15 seconds,
resetting the SCSI bus, at seemingly random times of disk access.

I tried upgrading to 2.1.126pre2, but got the same SCSI bus resets.

Downgrading to 2.1.123 fixes the problem.

Ben

-- 
Brought to you by the letters G and A and the number 9.
"Make a little birdhouse in your soul." -- They Might Be Giants
Debian GNU/Linux -- where do you want to go tomorrow? http://www.debian.org/
I'm on FurryMUCK as Che, and EFNet and YiffNet IRC as Che_Fox.

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/