[3643] in linux-scsi channel archive

home help back first fref pref prev next nref lref last post

Re: RE>DC390 errors (fwd)

daemon@ATHENA.MIT.EDU (Stephen Kitchener)
Tue Apr 7 16:16:46 1998

Date: 	Tue, 7 Apr 1998 20:12:09 +0000 (GMT)
From: Stephen Kitchener <root@g6dzj.demon.co.uk>
To: Michael Firkins <michael@sa.lyppard.com.au>
cc: linux SCSI <linux-scsi@vger.rutgers.edu>
In-Reply-To: <980406.125331@sa.lyppard.com.au>

On 6 Apr 1998, Michael Firkins wrote:
Hi Michael,

The IBM drive that I have is a DAS 34330 565A - is this close to the one
that you have ... ?

I was advised to disable the disconnection on the DC390, I have done this
but havn't stress tested this yet...

Any more info would be usefull

tia

> Hi.
> Funny, this sounds _very_ similar to the fault I sent to the list this 
> morning. The offending device for me seems to be an IBM DCAS hard 
> drive. Your problem sounds like it might be associated with an IBM hard 
> drive too. 
> 
> Is this co-incidence, configuration or conflageration?
> 
> Michael
> :-)
> 
> --------------------------------------
> Date: 6/4/98 12:41 PM
> To: Michael Firkins
> From: Stephen Kitchener
> Hi Guys,
> 
> Hope you can help, 
> I have been getting errors as follows
> 
> scsi : aborting command due to timeout : pid 917220, scsi0, channel 0, 
> id 4, lun 0 Write (6) 00 00 02 00 00
> -------------------------------------------------------------------------
> -
> scsi0 : AM53C974_abort called -- trouble starts!!
> AM53C974 register dump:
> IO base: 0x6400; CTCREG: 0x0000; CMDREG: 0x44; STATREG: 0x10; ISREG: 
> 0xc4
> CFIREG: 0x80; CNTLREG1-4: 0x57; 0x40; 0x18; 0x44
> DMACMD: 0x00; DMASTC: 0x0400; DMASPA: 0x3623800
> DMAWBC: 0x0000; DMAWAC: 0x3623c00; DMASTATUS: 0x00
> ---------------------------------------------------------
> scsi0: aborting disconnected command
> 
> Now this happens whenever I do anything that is at all intensive on any 
> of
> the devices on the bus. There are 3 scsi disk drives 1 tape drive and 
> one
> CD drive.
> 
> I have had this error when I do a tar from any of the disks to the tape
> drive, always reports scis0. or when I was trying to format the new IBM
> 4.3 drive that I got.
> 
> I have noticed something maybe, in that if I only have one disk drive
> mounted, it takes a long time for it to error, and then that shows 
> itself
> up as the tar has stopped. :-(. If I mount the other two scsi drives 
> into
> the directory free, is happens within a few minutes.
> 
> The system is a 166MMX Cyrix with 128MB Ram, running 2.0.33. RedHat4.2
> 
> Any more info, just ask. It's not on this machine, so will have to copy
> files if needed...
> 
> tia
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.rutgers.edu
> 

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
- S.M.Kitchener stephen@g6dzj.demon.co.uk                               -
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-


-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu

home help back first fref pref prev next nref lref last post