From: "Jeffrey W. Baker" <jwb@gghcwest.com>
To: linux-scsi@vger.kernel.org
Subject: rescan-scsi-bus.sh no longer unsafe with aic79xx
Date: 05 Jun 2003 11:01:48 -0700 [thread overview]
Message-ID: <1054836108.22202.10.camel@heat> (raw)
On 2.4.21-rc3/amd64 with previous aic79xx patches, use of
rescan-scsi-bus.sh had a tendency to hose the entire machine. If there
was a new device, aic79xx emitted a console message that it could not
allocate the new device. After that all I/O to the device failed, and
the rescan-scsi-bus.sh process was in the D state forever.
In the latest aic79xx, this no longer happens. rescan-scsi-bus.sh works
fine.
Cheers,
jwb
reply other threads:[~2003-06-05 17:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1054836108.22202.10.camel@heat \
--to=jwb@gghcwest.com \
--cc=linux-scsi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox