[4246] in linux-scsi channel archive
DC390 again
daemon@ATHENA.MIT.EDU (Stephen Kitchener)
Sun Jun 28 11:18:11 1998
Date: Sun, 28 Jun 1998 15:14:53 +0000 (GMT)
From: Stephen Kitchener <root@g6dzj.demon.co.uk>
Reply-To: Stephen Kitchener <root@g6dzj.demon.co.uk>
To: Linux SCSI <linux-scsi@vger.rutgers.edu>
Hi Guys,
I hope some one can help.
I must appologize firstly as I havn't been able to follow the current
discussions on SCSI and may have missed this...
I have two system each with DC390 but having different ROM versions on
board. On system 1 it is 1.6 and system 2 it is v 2.0.
On system 1 the kernel is 2.0.31 patched to work with an SCC card and
amatuer radio stuff. System 2 has 2.0.33 patched to do ISDN with an
internal ISDN Sedlbauer Speed Card. Apart from that they are standard from
when they were installed from RedHat 4.2.
I have a problem with SCSI timeouts on each system, but in differing ways.
System 1 has the following installed on the SCSI but but the ones marked *
are NOT mounted at boot time.
scsi0 : AM53/79C974 PCscsi driver rev. 0.5; host I/O address: 0x6400; irq:
9
scsi : 1 host.
Vendor: IBM Model: DCAS-34330 Rev: S65A
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sda at scsi0, channel 0, id 0, lun 0
Vendor: SEAGATE Model: ST52160N Rev: 0285
Type: Direct-Access ANSI SCSI revision: 02 *
Detected scsi disk sdb at scsi0, channel 0, id 1, lun 0
Vendor: SEAGATE Model: ST52160N Rev: 0285
Type: Direct-Access ANSI SCSI revision: 02 *
Detected scsi disk sdc at scsi0, channel 0, id 2, lun 0
Vendor: PLEXTOR Model: CD-ROM PX-20TS Rev: 1.00
Type: CD-ROM ANSI SCSI revision: 02
System 2 has these on the SCSI bus but those marked * are NOT mounted at
boot time.
scsi0 : AM53/79C974 PCscsi driver rev. 0.5; host I/O address: 0x6100; irq:
9
scsi : 1 host.
Vendor: SEAGATE Model: ST51080N Rev: 0943
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sda at scsi0, channel 0, id 0, lun 0
Vendor: SEAGATE Model: ST51080N Rev: 0943
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sdb at scsi0, channel 0, id 1, lun 0
Vendor: QUANTUM Model: FIREBALL_TM2110S Rev: 300X
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sdc at scsi0, channel 0, id 2, lun 0
Vendor: IBM Model: DCAS-34330 Rev: S65A
Type: Direct-Access ANSI SCSI revision: 02 *
Detected scsi disk sdd at scsi0, channel 0, id 4, lun 0
Vendor: PIONEER Model: CD-ROM DR-U12X Rev: 1.06
Type: CD-ROM ANSI SCSI revision: 02
Detected scsi CD-ROM sr0 at scsi0, channel 0, id 6, lun 0
System 1 works ok untill I mount the other disks and do updatedb, there
upon it, the DC390 gives a scsi timeout...
Jun 14 08:52:29 linux kernel: scsi : aborting command due to timeout : pid
22906, scsi0, channel 0, id 1, lun 0 0x08 1b c0 5a 02 00
Jun 14 08:52:29 linux kernel:
--------------------------------------------------------------------------
scsi0 : AM53C974_abort called -- trouble starts!!
AM53C974 register dump:
IO base: 0x6400; CTCREG: 0x0000; CMDREG: 0x42; STATREG: 0x11; ISREG: 0x54
CFIREG: 0x87; CNTLREG1-4: 0x57; 0x40; 0x18; 0x44
DMACMD: 0x00; DMASTC: 0x0400; DMASPA: 0x8f000
DMAWBC: 0x0000; DMAWAC: 0x8f400; DMASTATUS: 0x00
---------------------------------------------------------
scsi0 : abort failed, other command connected.
It dosn't matter if both or either are mounted, same result.
I can get the system to respond, as it goes very slow and the drive light
is on, by switching virtual screens under X. No idea why but it seems to
work.
On system 2 all is ok with the DC390. but after I mount the IBM, and try
and do mkfs on it I get the following...
scsi : aborting command due to timeout :
pid 3284, scsi0, channel 0, id 0, lun 0 0x08 01 cc 32 08 00
--------------------------------------------------------------------------
scsi0 : AM53C974_abort called -- trouble
starts!!
AM53C974 register dump:
IO base: 0x6100; CTCREG: 0x0000; CMDREG: 0x42; STATREG: 0x11; ISREG: 0x54
Jun 28 10:54:06 statler kernel: CFIREG: 0x87; CNTLREG1-4: 0x57; 0x40;
DMACMD: 0x00; DMASTC: 0x0400; DMASPA: 0x20a3000
DMAWBC: 0x0000; DMAWAC: 0x20a3400; DMASTATUS: 0x00
---------------------------------------------------------
scsi0 : abort failed, other command connected.
My question is:- is it the IBM drive that is causing me problems or is it
the DC 390 that is the culprit. System 1 seems fine when there is only the
IBM mounted on the system. But system 2 seems ok with everything mounted
other than the IBM mounted.
Help!!
If this has been asked before please excuse the intrusion but I would like
to know what's going on here.
tia
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
- S.M.Kitchener stephen@g6dzj.demon.co.uk -
-- If god had intended man to smoke - he would have set him on fire ----
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
