[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#339057: marked as done (linux-image-2.6.14-1-686: Cannot turn DMA on for /dev/hda)



Your message dated Wed, 5 Apr 2006 22:27:45 +0200
with message-id <20060405202745.GA23437@nancy>
and subject line Bug#339057: linux-image-2.6.14-1-686: Cannot turn DMA on for /dev/hda
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: linux-image-2.6.14-1-686
Version: 2.6.14-2
Severity: important

I have 2.6.12 and 2.6.14 (686 P4) installed on this machine. If I boot back into
2.6.12 DMA is on for /dev/hda. It is off in 2.6.14 and will not enable:

# hdparm -d 1 /dev/hda

/dev/hda:
 setting using_dma to 1 (on)
 HDIO_SET_DMA failed: Operation not permitted
 using_dma    =  0 (off)

This has, as you can imagine, very detrimental effects with ext3
filesystem responsiveness. Ugh!

DMA has worked in every kernel image I have used with this machine,
tracking Sid since summer 2003 with 2.4 and 2.6 kernels. Until now, that
is.

Please let me know what other information you might need. Here is a
hdparm -i just in case that helps.

/dev/hda:

 Model=HITACHI_DK23EA-60, FwRev=00K2A0A3, SerialNo=DZ4767
 Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
 RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
 BuffType=DualPortCache, BuffSize=2048kB, MaxMultSect=16, MultSect=16
 CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=117210240
 IORDY=yes, 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 udma3 udma4 *udma5
 AdvancedPM=yes: mode=0x80 (128) WriteCache=enabled
 Drive conforms to: ATA/ATAPI-5 T13 1321D revision 3:


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.14-1-686
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages linux-image-2.6.14-1-686 depends on:
ii  module-init-tools             3.2-pre9-4 tools for managing Linux kernel mo
ii  yaird [linux-initramfs-tool]  0.0.11-12  Yet Another mkInitRD

linux-image-2.6.14-1-686 recommends no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Version: 2.6.15-1

On Sun, 02 Apr 2006, Curt Howland wrote:

> This problem was solved with 2.6.15, and continues to work in 2.6.16, 
> so I figure it's ok to close the bugreport.
> 
> Thanks for all the help,
> 
> Curt-

should have been fixed with dropping the bogus modular-ide.patch.
closing as requested.
 
-- 
maks

--- End Message ---

Reply to: