From: "Michal Piotrowski" <michal.k.k.piotrowski@gmail.com>
To: "Zoltan Boszormenyi" <zboszor@dunaweb.hu>
Cc: 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 10:17:28 +0200 [thread overview]
Message-ID: <6bffcb0e0708160117m31b6edc6ta277b6ddf2d894f6@mail.gmail.com> (raw)
In-Reply-To: <46C2F526.30005@dunaweb.hu>
Hi Zoltan,
On 15/08/07, Zoltan Boszormenyi <zboszor@dunaweb.hu> wrote:
> Hi,
>
> I noticed that a bad CD of mine makes DMA disabled:
>
> hda: selected mode 0x44
> hda: cdrom_decode_status: status=0x51 { DriveReady SeekComplete Error }
> hda: cdrom_decode_status: error=0x40 { LastFailedSense=0x04 }
> ide: failed opcode was: unknown
> hda: cdrom_decode_status: status=0x51 { DriveReady SeekComplete Error }
> hda: cdrom_decode_status: error=0x40 { LastFailedSense=0x04 }
> ide: failed opcode was: unknown
> hda: cdrom_decode_status: status=0x51 { DriveReady SeekComplete Error }
> hda: cdrom_decode_status: error=0x40 { LastFailedSense=0x04 }
> ide: failed opcode was: unknown
> hda: cdrom_decode_status: status=0x51 { DriveReady SeekComplete Error }
> 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.
> Two things are interesting: first, it gets mounted correctly and
> readable and
> second, when DMA was already disabled no such messages occur in the logs.
> Anyhow, I would need DMA to correctly burn CDs/DVDs...
> What can I do besides manually re-enable DMA?
> All other disks I have tried behave perfectly.
> This happened on 2.6.22[-rcX], 2.6.23-rc3-git1 and 2.6.20-1.2962.fc6.
> This is on a Fedora Core 6 system. CD/DVD is using the old IDE drivers:
>
> Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
> ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
> NFORCE-MCP55: IDE controller at PCI slot 0000:00:04.0
> NFORCE-MCP55: chipset revision 161
> NFORCE-MCP55: not 100% native mode: will probe irqs later
> NFORCE-MCP55: BIOS didn't set cable bits correctly. Enabling workaround.
> NFORCE-MCP55: 0000:00:04.0 (rev a1) UDMA133 controller
> ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA
> Probing IDE interface ide0...
> hda: PIONEER DVD-RW DVR-111L, ATAPI CD/DVD-ROM drive
> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> Probing IDE interface ide1...
> ide-floppy driver 0.99.newide
>
> $ cat /proc/ide/amd74xx
> ----------AMD BusMastering IDE Configuration----------------
> Driver Version: 2.13
> South Bridge: 0000:00:04.0
> Revision: IDE 0xa1
> Highest DMA rate: UDMA133
> BM-DMA base: 0xf000
> PCI clock: 33.3MHz
> -----------------------Primary IDE-------Secondary IDE------
> Prefetch Buffer: yes yes
> Post Write Buffer: yes yes
> Enabled: yes no
> Simplex only: no yes
> Cable Type: 80w 80w
> -------------------drive0----drive1----drive2----drive3-----
> Transfer Mode: PIO DMA DMA DMA
> Address Setup: 30ns 90ns 90ns 90ns
> Cmd Active: 90ns 90ns 300ns 300ns
> Cmd Recovery: 30ns 30ns 300ns 300ns
> Data Active: 90ns 330ns 330ns 330ns
> Data Recovery: 30ns 270ns 270ns 270ns
> Cycle Time: 120ns 600ns 600ns 600ns
> Transfer Rate: 16.6MB/s 3.3MB/s 3.3MB/s 3.3MB/s
>
> Best regards,
> Zoltán Böszörményi
Regards,
Michal
--
LOG
http://www.stardust.webpages.pl/log/
next prev parent reply other threads:[~2007-08-16 8:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-15 12:44 Zoltan Boszormenyi
2007-08-16 8:17 ` Michal Piotrowski [this message]
2007-08-16 10:58 ` Zoltan Boszormenyi
2007-08-16 12:14 ` Zoltan Boszormenyi
[not found] <8Squ5-2cU-19@gated-at.bofh.it>
[not found] ` <8SIKl-5IK-13@gated-at.bofh.it>
2007-08-16 12:11 ` Bodo Eggert
2007-08-16 12:39 ` Zoltan Boszormenyi
2007-08-19 8:33 ` 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=6bffcb0e0708160117m31b6edc6ta277b6ddf2d894f6@mail.gmail.com \
--to=michal.k.k.piotrowski@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zboszor@dunaweb.hu \
/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
all inboxes | Powered by JetHome®