From: Jeff Garzik <jeff@garzik.org>
To: "\"J.A. Magallón\"" <jamagallon@ono.com>
Cc: Linus-IDE <linux-ide@vger.kernel.org>,
Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: The never enfind DRDY saga
Date: Thu, 08 May 2008 19:20:58 -0400 [thread overview]
Message-ID: <48238ADA.5060206@garzik.org> (raw)
In-Reply-To: <20080509005111.7cf55350@werewolf.home>
J.A. Magallón wrote:
> Hi all...
>
> I'm getting again my friendly DRDY errors, this time on the new disk I got
> to replace the old one (that fortunately was still under warranty...).
> This is a brand new disk, it came perfectly packaged...
> Now it is not a Seagate, but a WD:
Note that DRDY is not an error:
http://ata.wiki.kernel.org/index.php/Libata_error_messages
But moreover, for Serial ATA, timeouts are generally due to platform
problems, irq problems, or driver problems. When we see timeouts, we
generally do not look at the hard drive as the primary cause.
Have you gone through the debugging process for irq problems -- turning
off ACPI, noapic, etc.?
Jeff
next prev parent reply other threads:[~2008-05-08 23:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-08 22:51 The never enfind DRDY saga J.A. Magallón
2008-05-08 23:20 ` Jeff Garzik [this message]
2008-05-08 23:23 ` J.A. Magallón
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=48238ADA.5060206@garzik.org \
--to=jeff@garzik.org \
--cc=jamagallon@ono.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