From: Mark Lord <liml@rtr.ca>
To: Tejun Heo <htejun@gmail.com>
Cc: Jeff Garzik <jgarzik@pobox.com>, Alan Cox <alan@redhat.com>,
IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: libata fails to recover from HSM violation involving DRQ status
Date: Sat, 28 Apr 2007 16:18:04 -0400 [thread overview]
Message-ID: <4633ABFC.1020606@rtr.ca> (raw)
In-Reply-To: <4633AB75.7070107@rtr.ca>
Mark Lord wrote:
> Tejun,
>
> While working on the new hdparm (version 7.0, released today),
> I ran into trouble when a buggy SG_IO/ATA_16 packet caused
> the libata EH to get confused.
>
> I triggered this by accident, issuing an IDENTIFY command
> which incorrectly specified ATA_PROT_NODATA. My error, for sure,
> but libata never recovered from the "stuck DRQ bit" that resulted.
...
This was on 2.6.21, with ata_piix.
Cheers
next prev parent reply other threads:[~2007-04-28 20:18 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-28 20:15 libata fails to recover from HSM violation involving DRQ status Mark Lord
2007-04-28 20:18 ` Mark Lord [this message]
2007-04-28 20:30 ` Alan Cox
2007-04-28 20:37 ` Jeff Garzik
2007-04-28 20:44 ` Mark Lord
2007-04-28 20:50 ` Jeff Garzik
2007-04-28 21:25 ` Alan Cox
2007-04-28 21:35 ` Mark Lord
2007-04-28 21:38 ` Jeff Garzik
2007-04-28 21:41 ` Mark Lord
2007-04-29 3:17 ` Tejun Heo
2007-04-29 3:46 ` Jeff Garzik
2007-04-29 7:45 ` Tejun Heo
2007-04-29 3:51 ` Tejun Heo
2007-04-29 11:56 ` Mark Lord
2007-04-29 12:59 ` Mark Lord
2007-04-29 13:13 ` Mark Lord
2007-04-29 16:42 ` Tejun Heo
2007-04-29 16:47 ` Mark Lord
2007-04-29 18:49 ` Mark Lord
2007-04-29 19:05 ` Mark Lord
2007-04-30 0:59 ` Tejun Heo
2007-04-29 19:07 ` Mark Lord
2007-04-30 0:54 ` Tejun Heo
2007-04-30 3:42 ` Mark Lord
2007-04-30 3:58 ` Tejun Heo
2007-04-30 17:47 ` Mark Lord
2007-05-01 0:23 ` Mark Lord
2007-05-01 2:47 ` Tejun Heo
2007-05-01 13:00 ` Mark Lord
2007-05-11 3:33 ` Mark Lord
2007-05-11 3:35 ` Mark Lord
2007-04-29 12:07 ` Mark Lord
2007-04-29 16:36 ` Tejun Heo
2007-04-28 23:56 ` Alan Cox
2007-04-28 22:09 ` Mark Lord
2007-04-29 3:04 ` Tejun Heo
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=4633ABFC.1020606@rtr.ca \
--to=liml@rtr.ca \
--cc=alan@redhat.com \
--cc=htejun@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.