From: Ryan Cresawn <cresawn@vaquero.LaRC.NASA.GOV>
To: ultralinux@vger.kernel.org
Subject: Re: SCSI strangeness on Ultra2
Date: Wed, 06 Oct 1999 19:04:41 +0000 [thread overview]
Message-ID: <marc-linux-ultrasparc-93924102709512@msgid-missing> (raw)
In-Reply-To: <marc-linux-ultrasparc-93923506202161@msgid-missing>
David S. Miller writes:
> From: Ryan Cresawn <cresawn@vaquero.LaRC.NASA.GOV>
> Date: Wed, 6 Oct 1999 14:08:24 -0400 (EDT)
>
> I'm having some trouble on my Ultra2 with the SCSI busses. If I am
> accessing the ZIP 250 drive on the second SCSI bus then it will
> really confuse the whole system. Keyboard doesn't take input,
> programs freeze their operation, X freezes for minutes and then
> begins to work. If you would like more info let me know.
>
> Aparently the ZIP drive does not like to negotiate sync/wide SCSI
> parameters, that is why the SCSI bus locked up and the chain needed
> to be reset.
>
> Happily all of my error recovery seems to work and you get things
> working after the timeout is hit and the scsi bus is reset.
The renegotiation information that appeared in dmesg was present at
boot time and was never repeated. The problem I had was that since I
was trying to copy about 40 MBs to the ZIP drive at once it froze
almost everything for minutes at a time, then would release it, then
would freeze again, then would release it...you get the idea.
Anyways, this pattern continued for maybe 30-45 minutes until the copy
operation was complete. It's true that I'm happy the computer didn't
permanently lock up, but I was unhappy to find my parallel port ZIP
drive on my PC to be much faster.
--
Ryan
next prev parent reply other threads:[~1999-10-06 19:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-06 18:08 SCSI strangeness on Ultra2 Ryan Cresawn
1999-10-06 18:51 ` David S. Miller
1999-10-06 19:04 ` Ryan Cresawn [this message]
1999-10-06 19:20 ` David S. Miller
1999-10-06 19:31 ` Ryan Cresawn
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=marc-linux-ultrasparc-93924102709512@msgid-missing \
--to=cresawn@vaquero.larc.nasa.gov \
--cc=ultralinux@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.