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:31:57 +0000 [thread overview]
Message-ID: <marc-linux-ultrasparc-93924297712090@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 15:04:41 -0400 (EDT)
>
> 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.
>
> The reset policy when a device locks up the SCSI bus is to
> turn off all "features" to that device, which includes synchronous
> data transfers and disconnect. The lack of disconnect is almost
> surely what is causing the problem, when a read/write is issued
> to the drive, that SCSI bus is effectively unusable by any other
> SCSI device on it until the ZIP drive completes the read/write
> request.
Just so you know, I didn't have the cable I needed to connect the ZIP
250 to esp0 but I did have another SCSI card handy. I installed esp1
and connected the ZIP 250 without trouble. There are no other SCSI
devices attached to it. The three other SCSI devices are on esp0.
Does this jive with your reasoning as to why the computer was
freezing?
Thanks for the patch. I'll apply it and let you know how it goes.
--
Ryan
prev parent reply other threads:[~1999-10-06 19:31 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
1999-10-06 19:20 ` David S. Miller
1999-10-06 19:31 ` Ryan Cresawn [this message]
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-93924297712090@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.