From: Michael Hill <mdhill@interlog.com>
To: linux@cthulhu.engr.sgi.com
Subject: Re: wd33c93 errors.
Date: Thu, 22 Jan 1998 20:28:50 -0500 [thread overview]
Message-ID: <199801230128.UAA02293@mdhill.interlog.com> (raw)
In-Reply-To: <Pine.LNX.3.95.980122175054.21753I-100000@lager.engsoc.carleton.ca>
Alex deVries writes:
>
> 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).
>
The 1 G drive I posted about last week was made visible to IRIX by
modifying wd93_syncenable and wd93_syncperiod in
/var/sysgen/master.d/wd93 before recompiling the IRIX kernel. Does
anyone know of similar changes to the Linux source that would prevent
the system from hanging on startup with the following message?
sending SDTR 0103013f0csync_xfer=2cscsi : aborting command due to timeout : pid 7, scsi0, channel 0, id 3, lun 0 Inquiry 00 00
scsi0: Aborting connected command 7 - stopping DMA - sending wd33c93 ABORT command - flushing fifo - asr - 20, sr=ff, 16777215 by
- sending wd33c93 DISCONNECT command - asr = 20, sr=18.
If this is a bug, as Alan said, maybe there's hope for my drive, as
well as the one Alex has.
Thanks,
Mike
--
Michael Hill
Toronto, Canada
mdhill@interlog.com
next prev parent reply other threads:[~1998-01-23 1:31 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
1998-01-23 0:47 ` William J. Earl
1998-01-23 1:28 ` Michael Hill [this message]
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=199801230128.UAA02293@mdhill.interlog.com \
--to=mdhill@interlog.com \
--cc=linux@cthulhu.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