Yeah, thanks
This is not a Tekram board (smth like AMD PC SCSI onboard controller).
I've already checked all the cables and even chenged one of them. Nope,
it doesn't matter in this case. More to say, I have this very situation
with
two almost identical (different SCSI drives - Quantum and Seagate) PCs.
Will try to use 2.2.11 kernel and post the results.
SY,
raven
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Jean-Louis Debert
Sent: Friday, August 13, 1999 9:37 AM
To: [EMAIL PROTECTED]
Subject: Re: [expert] SCSI driver bug?
Kirill Bolshakov wrote:
> scsi: aborting command due to timeout : pid 44, scsi 0, channel 0, id
0,
> lun 0 Read (6) 03 c2 6b 68 00
>
> SCSI host0 abort (pid 44) timed out - resetting
> SCSI bus is being reset for host 0 channel 0.
>
> AM53C974_reset called
> AM53C974 register dump:
>
> IO base: 0xff00 CTCREG: 0x0000; CMDREG: 0x90; STATREG: 0x11; ISREG:
0xd4
> CFIREG: 0x80; CNTLREG1-4: 0x57; 0x40; 0x18; 0x44
> DMACMD: 0xc3; DMASTC: 0x0400; DMASPA: 0xe2b800
> DMAWBC: 0x0000; DMAWAC: 0xe2bc00; DMASTATUS: 0x08
You didn't say which kind of SCSI board you have.
There are two Linux drivers for the AM53C974. One is only for Tekram
(TRM390)
boards (those based on the AM53C974 chip) and the module is "tmscsim".
If you use a Tekram board you _must_ use the tmscsim module, the other
driver will not work properly. So be sure in that case to set your
conf.modules with a line saying "alias scsi_hostadapter tmscsim"
to be sure to select the right module.
If this is not your problem, then you could check your scsi cables
and termination on all scsi peripherals, most scsi problems come
from a bad electrical connection.
--
Jean-Louis Debert [EMAIL PROTECTED]
74 Annemasse France
old Linux fan
