public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tomasz Chmielewski <mangoo@interia.pl>
To: 7eggert@gmx.de
Cc: Andre Tomt <andre@tomt.net>, linux-kernel@vger.kernel.org
Subject: Re: [SATA] status reports updated
Date: Sat, 16 Apr 2005 12:58:18 +0200	[thread overview]
Message-ID: <4260EFCA.5040100@interia.pl> (raw)
In-Reply-To: <E1DMaM1-0001WQ-C6@be1.7eggert.dyndns.org>

Bodo Eggert <harvested.in.lkml@posting.7eggert.dyndns.org> wrote:
> Bodo Eggert <harvested.in.lkml@posting.7eggert.dyndns.org> wrote:
> 
>>Tomasz Chmielewski <mangoo@interia.pl> wrote:
> 
> 
>>>Is there a way to check what firmware a drive has
>>
>>The obvious one: hdparm
> 
> 
> <Ingrid>
> Or, since hdparm doesn't work for SCSI devices,
> cat /sys/block/sd$n/device/rev
> 
> (might depend on the vendor)

Oh, indeed!

# cat /sys/block/sda/device/rev
3.01

So what about SATA blacklisting based on a model/firmware version rather 
than on a model only?

My model (ST3200822AS) is blacklisted, though I'm stress-testing it for 
the second day and nothing happened, so I assume I may not be affected.

The question is, if I'm not affected because:
1) I'm lucky and it didn't happen yet,
2) hard drive (ST3200822AS) firmware is better - is anyone in contact 
with Seagate?
3) SATA controller (Silicon Image SiI 3112) BIOS is better - is anyone 
in contact with Silicon Image?


Additional question: is there a way to check the SATA controller BIOS as 
easily as it is with the drive firmware?


Tomek

----------------------------------------------------------------------
Startuj z INTERIA.PL! >>> http://link.interia.pl/f186c 


  reply	other threads:[~2005-04-16 10:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3THXg-6HX-5@gated-at.bofh.it>
     [not found] ` <3THXg-6HX-7@gated-at.bofh.it>
     [not found]   ` <3THXg-6HX-9@gated-at.bofh.it>
     [not found]     ` <3THXg-6HX-11@gated-at.bofh.it>
     [not found]       ` <3THXg-6HX-3@gated-at.bofh.it>
2005-04-15 23:36         ` [SATA] status reports updated Bodo Eggert <harvested.in.lkml@posting.7eggert.dyndns.org>
2005-04-16 10:58           ` Tomasz Chmielewski [this message]
     [not found] <3TDAh-38r-11@gated-at.bofh.it>
     [not found] ` <3TEd3-3xO-5@gated-at.bofh.it>
     [not found]   ` <3TEGb-42w-27@gated-at.bofh.it>
     [not found]     ` <3TEZi-4eW-7@gated-at.bofh.it>
2005-04-15 22:49       ` Bodo Eggert <harvested.in.lkml@posting.7eggert.dyndns.org>
2005-04-15 18:09 Jeff Garzik
2005-04-15 18:19 ` Joe Harvell
2005-04-15 18:29   ` Jeff Garzik
2005-04-15 19:01     ` Joe Harvell
2005-04-15 18:55 ` Tomasz Chmielewski
2005-04-15 19:22   ` Andre Tomt
2005-04-15 19:37     ` Tomasz Chmielewski
2005-04-15 23:27       ` Måns Rullgård
2005-04-16  2:36 ` Andy Lutomirski

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=4260EFCA.5040100@interia.pl \
    --to=mangoo@interia.pl \
    --cc=7eggert@gmx.de \
    --cc=andre@tomt.net \
    --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