From: Ross Biro <ross.biro@gmail.com>
To: Jim Gifford <maillist@jg555.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Random IDE Lock ups with via IDE
Date: Thu, 26 May 2005 15:35:33 -0400 [thread overview]
Message-ID: <8783be6605052612354c09ab8b@mail.gmail.com> (raw)
In-Reply-To: <42961567.1010906@jg555.com>
If you are using the legacy IDE layer you want to tweak WAIT_CMD. For
testing, you can make it really large and see if that impacts your
problem. A drive vendor once told me that it could take more than a
minute for an IDE drive to complete a command. I no longer purchase
drives from that vendor.
I'm not sure what libata uses, but my guess is it defaults it from the
SCSI layer.
If tweaking these time outs make your problem go away, odds are what
happened was that your drive remapped a few more bad sectors and now
takes a little too long to complete commands. The linux ide error
recovery code does a WIN_IDLE_IMMEDIATE when there is a problem. This
is allowed by the ATA-2 spec, but confuses most modern drives. So
once you start getting errors, often the drive gets so confused, you
never stop.
Ross
On 5/26/05, Jim Gifford <maillist@jg555.com> wrote:
> What do you recommend trying?
>
next prev parent reply other threads:[~2005-05-26 19:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-24 23:27 Random IDE Lock ups with via IDE Jim Gifford
2005-05-25 17:50 ` Jim Gifford
2005-05-25 20:34 ` Ross Biro
2005-05-25 20:46 ` Jim Gifford
2005-05-25 23:57 ` Ross Biro
2005-05-26 18:28 ` Jim Gifford
2005-05-26 19:35 ` Ross Biro [this message]
2005-05-26 19:50 ` Jeff Garzik
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=8783be6605052612354c09ab8b@mail.gmail.com \
--to=ross.biro@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maillist@jg555.com \
/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