From: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
To: Terry Barnaby <terry@beam.ltd.uk>
Cc: Michael Madore <mmadore@aslab.com>,
"Justin T. Gibbs" <gibbs@scsiguy.com>,
linux-kernel@vger.kernel.org
Subject: Re: Reproducible SCSI Error with Adaptec 7902
Date: Sat, 15 Mar 2003 14:11:48 +0100 [thread overview]
Message-ID: <20030315141148.A626@nightmaster.csn.tu-chemnitz.de> (raw)
In-Reply-To: <3E7200B7.6000907@beam.ltd.uk>; from terry@beam.ltd.uk on Fri, Mar 14, 2003 at 04:17:59PM +0000
On Fri, Mar 14, 2003 at 04:17:59PM +0000, Terry Barnaby wrote:
> The Seagate ST336607LW has firmware: 0004.
> Seagate have stated to me that this is the latest.
> They have also stated to me:
>
> Issuing an unrecognized or illegal command to the drive can cause the
> drive to go into a hardware fault mode where it will no longer respond,
> and may or may not respond to a SCSI BUS reset. It seems, in this case,
> the drive will no longer respond to any commands issued by the
> controller.
>
> Is this "feature" now common on SCSI drives ????
Could we add a KERN_WARNING printk in sd.c quoting/referencing
this message on inquiry detecting this device?
So sysadmins who are used to SCSI being robust could return the
drive to their vendors in exchange to a drive working along the
SCSI specs after reading this message.
Thanks in the name of the sysadmins.
Regards
Ingo Oeser
next prev parent reply other threads:[~2003-03-15 13:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-14 10:59 Terry Barnaby
2003-03-14 14:53 ` Justin T. Gibbs
2003-03-14 15:48 ` Terry Barnaby
2003-03-14 17:34 ` Justin T. Gibbs
2003-03-18 9:50 ` Terry Barnaby
2003-03-19 2:15 ` Justin T. Gibbs
2003-03-20 10:07 ` Terry Barnaby
2003-03-14 16:18 ` Michael Madore
2003-03-14 16:17 ` Terry Barnaby
2003-03-14 17:35 ` Justin T. Gibbs
2003-03-15 13:11 ` Ingo Oeser [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-17 16:30 Cress, Andrew R
2003-03-18 9:37 ` Terry Barnaby
2003-01-07 16:49 Michael Madore
2003-01-07 19:32 ` Justin T. Gibbs
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=20030315141148.A626@nightmaster.csn.tu-chemnitz.de \
--to=ingo.oeser@informatik.tu-chemnitz.de \
--cc=gibbs@scsiguy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mmadore@aslab.com \
--cc=terry@beam.ltd.uk \
/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
all inboxes | Powered by JetHome®