linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: Diego Calleja <diegocg@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: Faulty seagate drives, are going to be blacklisted?
Date: Tue, 20 Jan 2009 18:30:27 -0600	[thread overview]
Message-ID: <49766CA3.7090508@shaw.ca> (raw)
In-Reply-To: <20090120162612.7473aadf@diego-desktop>

Diego Calleja wrote:
> El Mon, 19 Jan 2009 20:55:05 -0600, Robert Hancock <hancockr@shaw.ca> escribió:
> 
>> There are a few drives which are currently marked to disable NCQ and 
>> warn the user that the firmware that should be upgraded:
>>
>> ST31500341AS
>> ST31000333AS
>> ST3640623AS
>> ST3640323AS
>> ST3320813AS
>> ST3320613AS
>>
>> all for firmware versions SD15 through SD19.
> 
> 
> Yes, I saw them, but apparently the NCQ bug is unrelated to this one.

I suspect it might be related, given that the firmware versions seem to 
partially overlap.

With this issue though, there isn't anything the kernel can do about the 
problem, so blacklisting doesn't seem to really make much sense.

  reply	other threads:[~2009-01-21  0:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-19 23:29 Faulty seagate drives, are going to be blacklisted? Diego Calleja
2009-01-20  0:22 ` David Rees
2009-01-20  2:55 ` Robert Hancock
2009-01-20 15:26   ` Diego Calleja
2009-01-21  0:30     ` Robert Hancock [this message]
2009-01-26 19:04   ` Felix Miata
2009-01-26 19:54     ` Mark Lord
2009-01-26 20:57       ` Gene Heskett
2009-01-26 21:34         ` Felix Miata
2009-01-26 23:56         ` Mark Lord
2009-01-20  3:32 ` Valdis.Kletnieks
2009-01-20 15:30   ` Diego Calleja
2009-01-20 17:24     ` Valdis.Kletnieks
2009-01-20 18:18       ` Diego Calleja
2009-01-21 10:27 ` Patrick Horn
2009-01-25  1:12   ` Tejun Heo

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=49766CA3.7090508@shaw.ca \
    --to=hancockr@shaw.ca \
    --cc=diegocg@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).