[Hardy] DMA not enabled on cdrom drive

[Scott Beamer]

Binary package hint: linux-source-2.6.24

When I launched k3b today it informed me that DMA was disabled on one of my DVD drives (Pioneer DVR-111C). This has not been a problem in the past. It was always enabled by default on this drive (as well as my other TSSTCorp DVD Drive).

I had to manually enable it.

This should not be the case.

[Pasku (pasku)]

I can confirm this BUG.
Also only occurs with one of my DVD drives (PIONEER DVD-RW DVR-109).

$ sudo hdparm -iI /dev/hda

/dev/hda:

 Model=PIONEER DVD-RW DVR-109, FwRev=1.58, SerialNo=
 Config={ Fixed Removeable DTR<=5Mbs DTR>10Mbs nonMagnetic }
 RawCHS=0/0/0, TrkSize=0, SectSize=0, ECCbytes=0
 BuffType=13395, BuffSize=64kB, MaxMultSect=0
 (maybe): CurCHS=0/0/0, CurSects=0, LBA=yes, LBAsects=0
 IORDY=on/off, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120}
 PIO modes: pio0 pio1 pio2 pio3 pio4
 DMA modes: mdma0 mdma1 mdma2
 UDMA modes: udma0 udma1 udma2
 AdvancedPM=no
 Drive conforms to: Unspecified: ATA/ATAPI-2,3,4,5

 * signifies the current active mode

ATAPI CD-ROM, with removable media
 Model Number: PIONEER DVD-RW DVR-109
 Serial Number: EADL079007WL
 Firmware Revision: 1.58
Standards:
 Likely used CD-ROM ATAPI-1
Configuration:
 DRQ response: 50us.
 Packet size: 12 bytes
Capabilities:
 LBA, IORDY(can be disabled)
 Buffer size: 64.0kB
 DMA: mdma0 mdma1 mdma2 udma0 udma1 *udma2
      Cycle time: min=120ns recommended=120ns
 PIO: pio0 pio1 pio2 pio3 pio4
      Cycle time: no flow control=240ns IORDY flow control=120ns
Commands/features:
 Enabled Supported:
    * Power Management feature set
    * PACKET command feature set
    * DEVICE_RESET command
HW reset results:
 CBLID- below Vih
 Device num = 0 determined by the jumper

$ dmesg | grep hda

[ 13.497220] ide0: BM-DMA at 0xff00-0xff07, BIOS settings: hda:DMA, hdb:DMA
[ 15.069713] hda: PIONEER DVD-RW DVR-109, ATAPI CD/DVD-ROM drive
[ 15.069722] hda: host max PIO5 wanted PIO255(auto-tune) selected PIO4
[ 15.069769] hda: UDMA/33 mode selected
[ 15.069844] hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }
[ 15.069848] hda: set_drive_speed_status: error=0x04 { AbortedCommand }
[ 15.069853] hda: host max PIO5 wanted PIO255(auto-tune) selected PIO4
[ 16.402337] hda: ATAPI 40X DVD-ROM DVD-R CD-R/RW drive, 2000kB Cache
[ 6900.970192] hda: drive_cmd: status=0x01 { Error }
[ 6900.970201] hda: drive_cmd: error=0x04 { AbortedCommand }

[Ilya Mezhirov (alih)]

I confirm this bug on Asus A6R laptop. Another Linux (Vector) works fine.

[Ilya Mezhirov (alih)]

What I actually had was bug #175022, which manifests itself in the same way, but it's not that easy to enable DMA. My problem is solved now. Maybe this bug is the same as #175022, I don't know.

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[Launchpad Janitor (janitor)]

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

[Bryan Wu (cooloney)]

As there is no any updates of this bug and it was reported to be solved. I will set the status to won't fix now.

-Bryan