mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Markus <M4rkusXXL@web.de>
To: lkml <linux-kernel@vger.kernel.org>
Subject: Seagate Barracuda 7200.11 ST31500341AS fw SD17
Date: Tue, 2 Jun 2009 12:58:20 +0200	[thread overview]
Message-ID: <200906021258.20346.M4rkusXXL@web.de> (raw)

Hello!

I have some Seagate Barracuda 7200.11 ST31500341AS 1.5TB drives. They 
use the firmware SD17.
They time out at the flush write cache and sometimes on the identify 
command.
I know that sounds suspicious so I wrote to seagate but they told me my 
drives are ok. (Although I dont think so.)

This drive+fw is blacklisted in the kernel, but there is no firmware 
upgrade for these drives. (Only very few serial numbers are able to 
upgrade.)

Now I want to know after what period of the time the kernel timeouts at 
these commands!? And if this timeout can be increased (manually, small 
patch for the kernel) and the min/max/avg time could somehow be 
messured. Every timeout kicks the drives off the raid, so I disabled 
the write cache (hdparm -W0 /dev/sdx) but thats no solution, just a bad 
workaround.

Its a amd64 system with the 2.6.29.4 on an AM3 board with AMDs 790GX + 
SB750 Chipsets running in ahci mode.

Thanks for your time and support!

Markus

PS: Please CC me!

             reply	other threads:[~2009-06-02 10:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-02 10:58 Markus [this message]
     [not found] ` <4A250B6A.6030904@grupopie.com>
2009-06-02 11:37   ` Markus
2009-06-02 12:14     ` Kay Diederichs
2009-06-02 12:38       ` Markus
2009-06-02 14:03         ` Krzysztof Halasa
2009-06-03 10:14           ` Markus
2009-06-03 15:38             ` Krzysztof Halasa
2009-06-03  4:10 ` Robert Hancock
2009-06-03 10:16   ` Markus

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=200906021258.20346.M4rkusXXL@web.de \
    --to=m4rkusxxl@web.de \
    --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

all inboxes | Powered by JetHome®