Messages in this thread | | | Date | Sat, 17 Jan 1998 15:24:07 +0100 (CET) | From | "Andreas Fredriksson (kernel account)" <> | Subject | A3940UW bus resets with zip drive |
| |
Hi all, here's some feedback on the aic7xxx driver. I bought an internal scsi zip drive yesterday, and I'm having some problems using it. My controller is a combined Adaptec 3940UW / Creative Vibra16 on an Asus media bus. The vibra16 part works fine with the native kernel sb16 drivers! :-)
The logs flood with a lot of "timed out.." entries followed by scsi bus resets, which are pretty tiresome (15 second lockup).
Everything worked nicely until I installed the zip. Tried both with SCB paging on/off -- same behaviour.
System is a PPro200 w/ 80MB ram. No IDE or floppy connected.
During booting (there was no disk in the zip, therefore the complaints):
aic7xxx: <Adaptec AIC-7880 Ultra SCSI host adapter> at PCI 13 aic7xxx: BIOS enabled, IO Port 0xd800, IO Mem 0xf9800000, IRQ 10, Revision B aic7xxx: Wide Channel, SCSI ID 7, 16/16 SCBs, QFull 16, QMask 0x1f scsi0 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 4.1.1/3.2.1 scsi : 1 host. scsi0: Scanning channel A for devices. Vendor: QUANTUM Model: FIREBALL ST3.2S Rev: 0F0C Type: Direct-Access ANSI SCSI revision: 02 Detected scsi disk sda at scsi0, channel 0, id 2, lun 0 Vendor: IOMEGA Model: ZIP 100 Rev: J.03 Type: Direct-Access ANSI SCSI revision: 02 Detected scsi removable disk sdb at scsi0, channel 0, id 3, lun 0 Vendor: NEC Model: CD-ROM DRIVE:502 Rev: 2.0y Type: CD-ROM ANSI SCSI revision: 02 scsi : detected 2 SCSI disks total. SCSI device sda: hdwr sector= 512 bytes. Sectors= 6328861 [3090 MB] [3.1 GB] sdb : READ CAPACITY failed. sdb : status = 1, message = 00, host = 0, driver = 28 sdb : extended sense code = 2 sdb : block size assumed to be 512 bytes, disk size 1GB.
Now check out the following (_with_ a disk in the zip :-) :
root@sanitarium# cat /dev/sdb > dump [ no errors ]
root@sanitarium# mount /dev/sdb4 /mnt/zip -t ext2 root@sanitarium# mount ... /dev/sdb4 on /mnt/zip type ext2 (rw) root@sanitarium# cd /mnt/zip root@sanitarium# cp -av big_directory . [filenames roll by] ... now the screen floods with scsi messages:
As you can see there are timeouts in both reading and writing, it seems the whole scsi bus is locked!
Jan 17 15:02:22 sanitarium kernel: scsi : aborting command due to timeout : pid 3741, scsi0, channel 0, id 3, lun 0 Write (6) 01 95 b8 f4 00 Jan 17 15:02:22 sanitarium kernel: scsi : aborting command due to timeout : pid 3742, scsi0, channel 0, id 2, lun 0 Read (10) 00 00 32 6b fd 00 00 02 00 Jan 17 15:02:22 sanitarium kernel: scsi : aborting command due to timeout : pid 3743, scsi0, channel 0, id 2, lun 0 Read (10) 00 00 32 6b ff 00 00 02 00 Jan 17 15:02:22 sanitarium kernel: scsi : aborting command due to timeout : pid 3744, scsi0, channel 0, id 3, lun 0 Write (6) 01 96 ac f4 00 Jan 17 15:02:23 sanitarium kernel: SCSI host 0 abort (pid 3741) timed out - resetting Jan 17 15:02:23 sanitarium kernel: SCSI bus is being reset for host 0 channel 0. Jan 17 15:03:15 sanitarium kernel: scsi : aborting command due to timeout : pid 4197, scsi0, channel 0, id 3, lun 0 Write (6) 00 4c 8c f4 00 Jan 17 15:03:15 sanitarium kernel: scsi : aborting command due to timeout : pid 4198, scsi0, channel 0, id 3, lun 0 Write (6) 00 4d 80 f4 00 Jan 17 15:03:16 sanitarium kernel: SCSI host 0 abort (pid 4197) timed out - resetting Jan 17 15:03:16 sanitarium kernel: SCSI bus is being reset for host 0 channel 0. Jan 17 15:03:17 sanitarium kernel: Ouch, no kerneld for message 2147418157
// Andreas (dep@trekab.se)
| |