From: Zoltan Boszormenyi <zboszor@dunaweb.hu>
To: 7eggert@gmx.de
Cc: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: Bad CD disk disables IDE DMA
Date: Thu, 16 Aug 2007 14:39:25 +0200 [thread overview]
Message-ID: <46C4457D.5030703@dunaweb.hu> (raw)
In-Reply-To: <E1ILeCg-0000iH-2W@be1.lrz>
Bodo Eggert írta:
> Michal Piotrowski <michal.k.k.piotrowski@gmail.com> wrote:
>
>> On 15/08/07, Zoltan Boszormenyi <zboszor@dunaweb.hu> wrote:
>>
>
>
>>> I noticed that a bad CD of mine makes DMA disabled:
>>>
>
> [...]
>
>>> hda: cdrom_decode_status: error=0x40 { LastFailedSense=0x04 }
>>> ide: failed opcode was: unknown
>>> hda: DMA disabled
>>> hda: ide_intr: huh? expected NULL handler on exit
>>> hda: ATAPI reset complete
>>>
>>> Every time I put the said CD into to drive and DMA is on, I get the
>>> above messages.
>>>
>> This might be intended.
>>
>
> Maybe, and maybe only a certain effect might be intended. And maybe I can
> help by asking these questions:
>
> 1) Does disabling DMA fix the seek errors, or does it hide them by the PIO
> interfce not printing them?
>
With DMA off no seek error occurs. When the transfer rate is
limited to UDMA3 I get this:
hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
hda: drive_cmd: error=0x04 { AbortedCommand }
ide: failed opcode was: 0xec
Note the difference: the error code is different and
it knows the failed opcode as well. But DMA remains on.
Can it be a bad 80w cable? I don't think so, considering that
it doesn't occur for DVDs when using UDMA4...
> 2) If it does hide them, would filtering for seek errors be a sane thing to
> do, or does the DMA engine (or HDD) behave badly on these errors, or
> do bad-DMA devices report seek errors, too?
>
> 3) If it does not hide them, would re-enabling DMA on disk change be a
> feasable workaround?
> (proposed interface: use hdparm -d $num where $num =
> 0, 1: as before
> 3: DMA on, if switched off automatically, will be set to 2
> 2: DMA off, will be turned on (set to 3) on disk change)
>
The automatic DMA re-enabling would be a good solution.
> 4) Does libata work well enough for making all effort put into that old
> IDE layer be a waste of time?
>
Unfortunately libata (or pata_amd) doesn't work very well on this machine,
I tried to switch to libata for the CD drive but it lost the DVD-playing
capability.
It seems the error was that libdvdcss couldn't get the keys via the scd
device.
This is the main obstacle that stops me switching to Fedora 7 from FC6.
I reported it some time ago but got no answer. Look for subject
"DVD-playing, ide-cd vs scsi-cd drivers".
Best regards,
Zoltán Böszörményi
next prev parent reply other threads:[~2007-08-16 12:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8Squ5-2cU-19@gated-at.bofh.it>
[not found] ` <8SIKl-5IK-13@gated-at.bofh.it>
2007-08-16 12:11 ` Bad CD disk disables IDE DMA Bodo Eggert
2007-08-16 12:39 ` Zoltan Boszormenyi [this message]
2007-08-19 8:33 ` Zoltan Boszormenyi
[not found] <46C2F526.30005@dunaweb.hu>
2007-08-16 8:17 ` Michal Piotrowski
2007-08-16 10:58 ` Zoltan Boszormenyi
2007-08-16 12:14 ` Zoltan Boszormenyi
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=46C4457D.5030703@dunaweb.hu \
--to=zboszor@dunaweb.hu \
--cc=7eggert@gmx.de \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.com \
/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).