[Top] [All Lists]

Re: wd33c93 errors.

To: Alan Cox <>
Subject: Re: wd33c93 errors.
From: Alex deVries <>
Date: Thu, 22 Jan 1998 18:07:27 -0500 (EST)
In-reply-to: <>
On Thu, 22 Jan 1998, Alan Cox wrote:
> > repartitioned it from Irix, and mounted it as an EFS partition under Irix
> > just fine.  That would seem to indicate that everything is alright with
> Including rewriting it ?

Ah, I tried that specifically, and had problems too with Irix.  So, the
disk is toast, and it'll go back to the storage room I found it in (along
with an AXP).

> > scsi0: Aborting connected command 17577 - stopping DMA - sending wd33c93
> > ABORT command - flushing fifo - asr = 25, sr=ff, 16777215 bytes
> > un-transferred (timeout=-1) - sending wd33c93 DISCONNECT command = asr=00,
> > sr=18.
> > And the whole thing is hung, hard.
> Thats a bug. 

I've got a WO recordable CDROM also. I can change directories on it just
fine, but when reading a lot of data on it, it'll give me:

scsi : aborting command due to timeout : pid 2282, scsi0, channel 0, id 2,
lun 0 Write (6) 00 0a 99 02 00
scsi0: Abort - removing command 2282 from input_Q.

And then a total hang again.. no numlock, no pinging.

I can't test the recordable CDROM under Irix because it doesn't have a
WORM driver built in.

Now, another thing... I have a _functional_ (under both Irix and Linux
) CDROM that doesn't get detected under Linux when I have all of this
other crap on the SCSI bus. It is perfectly usable if it's on the external
bus by itself, but not with other devices on the bus.

My conclusion is that my 700MB disk and recordable CDROM are crap, and the
Linux driver for the wd33c93 can't handle these kinds of problems

And lastly: having a cute blue case seemed pretty good at first, but it'd
be heavenly to have room for more than two hard disks inside.

Tomorrow I'll borrow a functional SCSI disk and try again.

- Alex "and as if SCSI hell weren't bad enough, I have to get my wisdom
teeth out" deVries

<Prev in Thread] Current Thread [Next in Thread>