From: ralf@uni-koblenz.de
To: fisher@sgi.com
Cc: Alex deVries <adevries@engsoc.carleton.ca>,
alan@lxorguk.ukuu.org.uk, linux@hollywood.engr.sgi.com,
William Fisher <fisher@hollywood.engr.sgi.com>
Subject: Re: wd33c93 errors.
Date: Sun, 25 Jan 1998 19:14:45 +0100 [thread overview]
Message-ID: <19980125191445.00880@uni-koblenz.de> (raw)
In-Reply-To: <199801230012.QAA28870@hollywood.engr.sgi.com>; from William Fisher on Thu, Jan 22, 1998 at 04:12:18PM -0800
On Thu, Jan 22, 1998 at 04:12:18PM -0800, William Fisher wrote:
> I am getting the details but it seems that something is amiss
> with the "standard" PC SCSI devices in this area. There is also
> some fuzzy-ness going on in the device type they are advertizing
> themselves to be. I will have the gory details shortly since we
> would like to understand the problem. We have had a couple of
> customers complain about this problem.
Certain revisions of the wd33c93 recognicable by the number group 00-04
and the word PROTO printed on them (at least in the DIL case) have a
problem in the microcode that may hang the chip until the next hardware
reset. Unfortunately tons of these prototype versions have been shipped.
The only way to run these chips reliable is to disable disconnect/reconnect.
By my experience it looks as if not all devices produce that type of
disconnect/reconnect bug. I never saw it happen for example during
lowlevel formatting a SCSI disk but attempting to use disconnect/reconnect
with QIC tapes was a 100% way for me to hang my system. No idea about
other types of devices.
Ralf
next prev parent reply other threads:[~1998-01-25 23:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-01-22 21:50 wd33c93 errors Alex deVries
1998-01-22 22:34 ` Alan Cox
1998-01-22 22:34 ` Alan Cox
1998-01-22 23:07 ` Alex deVries
1998-01-23 0:12 ` William Fisher
1998-01-23 0:12 ` William Fisher
1998-01-25 18:14 ` ralf [this message]
1998-01-23 0:47 ` William J. Earl
1998-01-23 1:28 ` Michael Hill
1998-01-23 4:08 ` ralf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19980125191445.00880@uni-koblenz.de \
--to=ralf@uni-koblenz.de \
--cc=adevries@engsoc.carleton.ca \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=fisher@hollywood.engr.sgi.com \
--cc=fisher@sgi.com \
--cc=linux@hollywood.engr.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox