[PARPORT] Re: SCSI Timeout on AIC7xxx when PPA is active.

Mark Garlanger (garlangr@cyberramp.net)
Thu, 28 May 1998 06:59:03 -0500

David Campbell wrote:

> > Date: Wed, 27 May 1998 22:20:50 -0500
> > From: Mark Garlanger <garlangr@cyberramp.net>
> > To: linux-parport@torque.net, linux-scsi@vger.rutgers.edu
> > Subject: [PARPORT] SCSI Timeout on AIC7xxx when PPA is active.
> > Hi all,
> >
> > Is anyone successfully running the AIC7xxx and PPA drivers togather?
> > When I try to use the PPA drive with the AIC7xxx driver, I am seeing
> > SCSI Timeout on the AIC7xxx driver during the booting.
> > I've tried both the stock ppa driver and the latest 1.42 version. The
> > AIC7xxx is the stock 2.0.33 driver.
> > Could there be some interaction in the mid-level scsi routines between
> > the aic7xxx and ppa drivers?
> Hmm...
> Could you fire up your system in the following senarios (assuming root
> partition on the HDD):
> 1) Zip drive unplugged but driver still in the kernel

Here is the dmesg with SMP and 1):

furball:~$ dmesg
Intel MultiProcessor Specification v1.4
    Virtual Wire compatibility mode.
OEM ID: INTEL Product ID: 440FX APIC at: 0xFEE00000
Processor #1 Pentium(tm) Pro APIC version 17
Processor #0 Pentium(tm) Pro APIC version 17
I/O APIC #2 Version 17 at 0xFEC00000.
Processors: 2
Console: 16 point font, 400 scans
Console: colour VGA+ 80x25, 1 virtual console (max 63)
pcibios_init : BIOS32 Service Directory structure at 0x000f6260
pcibios_init : BIOS32 Service Directory entry at 0xfd7d0
pcibios_init : PCI BIOS revision 2.10 entry at 0xfd9ef
Probing PCI hardware.
Calibrating delay loop.. ok - 179.40 BogoMIPS
Memory: 63164k/65536k available (792k kernel code, 384k reserved, 1196k data)

Swansea University Computer Society NET3.035 for Linux 2.0
NET3: Unix domain sockets 0.13 for Linux NET3.035.
Swansea University Computer Society TCP/IP for NET3.034
IP Protocols: ICMP, UDP, TCP
Checking 386/387 coupling... Ok, fpu using exception 16 error reporting.
Checking 'hlt' instruction... Ok.
Linux version 2.0.33 (Linux version 2.0.33 (garlangr@furball) (gcc version 2.7.2) #1 Wed May 27
21:18:40 CDT 1998
Booting processor 0 stack 00002000: Calibrating delay loop.. ok - 179.40
Total of 2 processors activated (358.81 BogoMIPS).
Starting kswapd v
Serial driver version 4.13 with no serial options enabled
tty00 at 0x03f8 (irq = 4) is a 16550A
tty01 at 0x02f8 (irq = 3) is a 16550A
lp0 at 0x0278, (polling)
Real Time Clock Driver v1.07
Sound initialization started
<Pro AudioSpectrum 16D rev 255> at 0x388 irq 11 dma 7
<Yamaha OPL3 FM> at 0x388
Sound initialization complete
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
aic7xxx: <Adaptec AIC-7880 Ultra SCSI host adapter> at PCI 8
aic7xxx: Loading serial EEPROM...done
aic7xxx: Termination (Low ON, High ON)
aic7xxx: BIOS enabled, IO Port 0xf400, IO Mem 0xf0dff000, IRQ 10, Revision B
aic7xxx: Extended translation enabled.
aic7xxx: Wide Channel, SCSI ID 7, 16/255 SCBs, QFull 16, QMask 0x1f
aic7xxx: Resetting channel A
aic7xxx: Downloading sequencer code... 416 instructions downloaded
ppa: Version 1.41
ppa: Probing port 0378
ppa: SPP port present
ppa: PS/2 bidirectional port present
ppa: EPP 1.9 with hardware direction protocol
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.
(scsi0:0:0:0) Using 16 bit(Wide) transfers.
(scsi0:0:0:0) Synchronous at 20.0MHz, offset 8.
  Vendor: MICROP Model: 3387WS Rev: x43h
  Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sda at scsi0, channel 0, id 0, lun 0
(scsi0:0:3:0) Synchronous at 4.0MHz, offset 15.
  Vendor: IBM Model: CDRM00201 !F Rev: 0724
  Type: CD-ROM ANSI SCSI revision: 02
Detected scsi CD-ROM sr0 at scsi0, channel 0, id 3, lun 0
(scsi0:0:5:0) Synchronous at 6.67MHz, offset 15.
  Vendor: ARCHIVE Model: Python 25501-XXX Rev: 5.45
  Type: Sequential-Access ANSI SCSI revision: 02
Detected scsi tape st0 at scsi0, channel 0, id 5, lun 0
(scsi0:0:0:0) Enabled tagged queuing, queue depth 8.
scsi : detected 1 SCSI tape 1 SCSI cdrom 1 SCSI disk total.
SCSI device sda: hdwr sector= 512 bytes. Sectors= 16992188 [8296 MB] [8.3 GB]

PPP: version 2.2.0 (dynamic channel allocation)
TCP compression code copyright 1989 Regents of the University of California
PPP Dynamic channel allocation code copyright 1995 Caldera, Inc.
PPP line discipline registered.
Partition check:
 sda: sda1 sda2 < sda5 sda6 sda7 sda8 > sda3 sda4
VFS: Mounted root (ext2 filesystem) readonly.
Adding Swap: 130748k swap-space (priority 2144)
registered device ppp0

> 2) Zip drive plugged in, turned on but no disk in drive

 Crash, copied the following messages by hand:
....standard boot messages...
sdb: READ CAPACITY unable to get size??
sdb ... assuming 1 GByte

.... other standard messages
.... Message about checking root parition R/O...
scsi : aborting command due to timeout : pid 45 scsi0, channel 0, id 0 , lun
0 0x08 00 02 81 0e 00
SCSI host 0 abort (pid 48) timed out - reset bus
SCSI bus is being reset for host 0 channel 0
(scsi0:0:0:0) Reset called, scb 0, flags 0x1

> 3) Zip drive plugged in, turned on but with a disk in drive

This was tried with both the SMP and non-SMP kernels: Same as 2 without the

> Expected results:
> 1) Everything OK - ppa driver does nothing
> 2) Everything OK - Minimal access to identify drive presence
> 3) Possible crash - A number of device accesses to read partition table
> The output of the "dmesg" command will shed more light on the problem.
> Also rebuild the kernel with ppa being a module. See if loading ppa as a
> module causes a problem (but only after performing the test runs above).

I'll try this probably tonight and let you know...

> If you can get the two drivers into the kernel together, try a bulk copy
> between the two drives (ie: copy a very large file).

If the module works I will try this also

> I have heard problems with ppa and other SCSI devices but I am not sure
> where the problem lies, on its own the ppa driver works (almost - well I
> haven't seen any problems lately) flawlessly. I have made large number of
> modifications to ensure the driver "yields" to other processes due to the
> low bandwith (0.6 MB/sec vs 10MB/sec). How this affects other low level
> SCSI drivers is unknown.
> My understanding of the mid-level SCSI protocol is that each device
> processes the pending data independent of other low level drivers. I stand
> to be corrected.

Your probably right, my guess was just a stab in the dark...


> David Campbell
> =======================================================
> campbell@torque.net
> "All parallel ports are equal - Some are more equal than others"

-- To unsubscribe, send mail to: linux-parport-request@torque.net --
-- with the single word "unsubscribe" in the body of the message. --

This archive was generated by hypermail 2.0b3 on Wed 30 Dec 1998 - 10:17:47 EST