From: Jeff Garzik <jeff@garzik.org>
To: "\"J.A. Magallón\"" <jamagallon@ono.com>
Cc: "Linux-Kernel, " <linux-kernel@vger.kernel.org>,
Linux IDE mailing list <linux-ide@vger.kernel.org>
Subject: Re: DRDY errors again
Date: Tue, 08 Apr 2008 11:59:51 -0400 [thread overview]
Message-ID: <47FB9677.30109@garzik.org> (raw)
In-Reply-To: <20080408171311.69441c8b@werewolf>
J.A. Magallón wrote:
> scsi4 : ata_piix
> scsi5 : ata_piix
> ata3: SATA max UDMA/133 cmd 0xc000 ctl 0xc400 bmdma 0xd000 irq 18
> ata4: SATA max UDMA/133 cmd 0xc800 ctl 0xcc00 bmdma 0xd008 irq 18
> ata4.00: ATA-8: ST3500820AS, SD25, max UDMA/133
> ata4.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 0/32)
> ata4.00: configured for UDMA/133
> ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> ata4.00: cmd b0/d8:00:00:4f:c2/00:00:00:00:00/00 tag 0
> res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata4.00: status: { DRDY }
Can you bisect to see when this problem starts? I'm pretty sure it's
software, either interrupt-related or the libata driver itself.
See http://ata.wiki.kernel.org/index.php/Libata_error_messages for a
full explanation of that error message.
Most notable: "DRDY" == device ready == device says everything is OK,
from it's perspective. "timeout" usually means an interrupt wasn't
delivered from your ATA controller, when we were expecting one.
Jeff
next prev parent reply other threads:[~2008-04-08 16:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-08 15:13 DRDY errors again J.A. Magallón
2008-04-08 15:59 ` Jeff Garzik [this message]
2008-04-13 0:26 ` J.A. Magallón
2008-04-20 22:41 ` J.A. Magallón
2008-04-08 21:40 ` Bernd Eckenfels
2008-04-09 3:42 ` Philippe Troin
2008-04-13 0:22 ` 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=47FB9677.30109@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