From: Tejun Heo <htejun@gmail.com>
To: Vlad Codrea <VladCodrea@mail.utexas.edu>
Cc: linux-ide@vger.kernel.org
Subject: Re: DVD drive fails in 2.6.20.2
Date: Wed, 14 Mar 2007 13:11:55 +0900 [thread overview]
Message-ID: <45F7760B.10102@gmail.com> (raw)
In-Reply-To: <45F631F7.6020106@mail.utexas.edu>
[-- Attachment #1: Type: text/plain, Size: 717 bytes --]
Vlad Codrea wrote:
> ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> ata2.00: (BMDMA stat 0x25)
> ata2.00: cmd a0/01:00:00:00:00/00:00:00:00:00/a0 tag 0 cdb 0x12 data 36 in
> res 58/00:02:00:24:00/00:00:00:00:00/a0 Emask 0x2 (HSM violation)
> ata2: soft resetting port
> ata2: port is slow to respond, please be patient (Status 0xd8)
> ata2: port failed to respond (30 secs, Status 0xd8)
> ATA: abnormal status 0xD8 on port 0x177
> ATA: abnormal status 0xD8 on port 0x177
Okay, now that you're on libata driver, it's easier for me to debug.
Can you apply the attached patch over 2.6.20 and report what the kernel
says? (the patch will apply with some noise, it's okay)
Thanks.
--
tejun
[-- Attachment #2: hsm-debug.patch --]
[-- Type: text/x-patch, Size: 1489 bytes --]
diff --git a/drivers/ata/libata-core.c b/drivers/ata/libata-core.c
index 14629a3..387235f 100644
--- a/drivers/ata/libata-core.c
+++ b/drivers/ata/libata-core.c
@@ -4453,9 +4453,13 @@ fsm_start:
if (likely(status & (ATA_ERR | ATA_DF)))
/* device stops HSM for abort/error */
qc->err_mask |= AC_ERR_DEV;
- else
+ else {
/* HSM violation. Let EH handle this */
+ ata_port_printk(ap, KERN_WARNING,
+ "!DRQ on HSM_ST_FIRST (0x%x)\n",
+ status);
qc->err_mask |= AC_ERR_HSM;
+ }
ap->hsm_task_state = HSM_ST_ERR;
goto fsm_start;
@@ -4547,13 +4551,17 @@ fsm_start:
if (likely(status & (ATA_ERR | ATA_DF)))
/* device stops HSM for abort/error */
qc->err_mask |= AC_ERR_DEV;
- else
+ else {
+ ata_port_printk(ap, KERN_WARNING,
+ "!DRQ on HSM_ST (0x%x)\n",
+ status);
/* HSM violation. Let EH handle this.
* Phantom devices also trigger this
* condition. Mark hint.
*/
qc->err_mask |= AC_ERR_HSM |
AC_ERR_NODEV_HINT;
+ }
ap->hsm_task_state = HSM_ST_ERR;
goto fsm_start;
@@ -4579,8 +4587,12 @@ fsm_start:
status = ata_wait_idle(ap);
}
- if (status & (ATA_BUSY | ATA_DRQ))
+ if (status & (ATA_BUSY | ATA_DRQ)) {
+ ata_port_printk(ap, KERN_WARNING,
+ "BUSY|DRQ on ERR|DF (0x%x)\n",
+ status);
qc->err_mask |= AC_ERR_HSM;
+ }
/* ata_pio_sectors() might change the
* state to HSM_ST_LAST. so, the state
next prev parent reply other threads:[~2007-03-14 4:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-13 5:09 DVD drive fails in 2.6.20.2 Vlad Codrea
2007-03-14 3:57 ` Tejun Heo
2007-03-14 4:11 ` Tejun Heo [this message]
2007-03-14 15:15 ` Vlad Codrea
2007-03-14 16:58 ` Vlad Codrea
2007-03-15 6:22 ` Tejun Heo
2007-03-15 14:00 ` Vlad Codrea
2007-03-15 17:57 ` Albert Lee
2007-03-16 2:58 ` Vlad Codrea
2007-03-16 16:34 ` Albert Lee
2007-03-16 18:09 ` Vlad Codrea
2007-03-17 4:43 ` Albert Lee
2007-03-18 1:26 ` Vlad Codrea
2007-03-18 10:57 ` Albert Lee
2007-03-19 5:58 ` Vlad Codrea
2007-03-19 6:48 ` Albert Lee
2007-03-19 7:01 ` Albert Lee
2007-03-19 13:22 ` Vlad Codrea
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=45F7760B.10102@gmail.com \
--to=htejun@gmail.com \
--cc=VladCodrea@mail.utexas.edu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).