From: Parag Warudkar <parag.warudkar@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Failure with SATA DVD-RW
Date: Thu, 6 Dec 2007 01:33:16 +0000 (UTC) [thread overview]
Message-ID: <loom.20071206T012459-620@post.gmane.org> (raw)
In-Reply-To: cd32a0620712041608o7733db74xf4975dec44925730@mail.gmail.com
Tom Lanyon <tomlanyon <at> gmail.com> writes:
> scsi4: ahci
> ata5: SATA link up at 1.5 Gbps (SStatus 113 SControl 300)
> ata5.00: ATAPI, max UDMA/66
> ata5.00: qc timeout (cmd 0xef)
> ata5.00: failed to set xfermode (err_mask=0x104)
> ata5.00: limiting speed to UDMA/44
> ata5: failed to recover some devices, retrying in 5 secs
> ata5: port is slow to respond, please be patient (Status 0x80)
> ata5: port failed to respond (30 secs, status 0x80)
> ata5: COMRESET failed (device not ready)
> ata5: hardreset failed, retrying in 5 secs
> ata5: SATA link up at 1.5 Gbps (SStatus 113 SControl 300)
> ata5.00: ATAPI, max UDMA/66
> ata5.00: qc timeout (cmd 0xef)
> ata5.00: failed to set xfermode (err_mask=0x104)
> ata5.00: limiting speed to PIO0
> ata5: failed to recover some devices, retrying in 5 secs
> ata5: port is slow to respond, please be patient (Status 0x80)
> ata5: port failed to respond (30 secs, status 0x80)
> ata5: COMRESET failed (device not ready)
> ata5: hardreset failed, retrying in 5 secs
> ata5.00: ATAPI, max UDMA/66
> ata5.00: qc timeout (cmd 0xef)
> ata5.00: failed to set xfermode (err_mask=0x104)
> ata5.00: disabled
>
Looks like it is trying to set transfer mode to UDMA/66 and failing. After
that it tried UDMA/44 and failed again. Next UDMA/66 again with unsurprising
result - failed. After that PIO0 which seems to cause some kind of trouble,
then it tries UDMA/66 again, and I am not stating the result again :) !
> Any ideas what to try to get it working under AHCI?
>
I recall reading somewhere - the Pioneer drive needs UDMA/33 which it did not
try in your case - need to some how have it try UDMA/33 but I don't find a
boot parameter which will do that. So may be adding a quirk for this device to
limit the xfer mode to 33 may work.
What does your dmesg output for the drives look like when you run in IDE
compat mode? (Particularly the DMA for this drive?)
Parag
next prev parent reply other threads:[~2007-12-06 1:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-05 0:08 Failure with SATA DVD-RW Tom Lanyon
2007-12-06 1:33 ` Parag Warudkar [this message]
2007-12-07 0:39 ` Andrew Morton
2007-12-07 0:40 ` Andrew Morton
2007-12-10 9:45 ` Tejun Heo
2007-12-07 2:12 ` 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=loom.20071206T012459-620@post.gmane.org \
--to=parag.warudkar@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).