Bug 15 - No dma on first hard drive
Summary: No dma on first hard drive
Alias: None
Product: IO/Storage
Classification: Unclassified
Component: IDE (show other bugs)
Hardware: IA-32 Linux
: P2 normal
Assignee: Alan
Depends on:
Reported: 2002-11-14 12:25 UTC by Nicolas Mailhot
Modified: 2005-12-11 03:09 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.5.47-ac3 to 2.5.73
Tree: Mainline
Regression: ---

dmesg (7.12 KB, text/plain)
2003-03-06 15:44 UTC, Nicolas Mailhot
lspci (7.18 KB, text/plain)
2003-03-06 15:45 UTC, Nicolas Mailhot
/sbin/hdparm -iI /dev/hda (2.05 KB, text/plain)
2003-03-06 15:46 UTC, Nicolas Mailhot
Kernel config (22.63 KB, text/plain)
2003-03-06 15:50 UTC, Nicolas Mailhot

Description Nicolas Mailhot 2002-11-14 12:25:44 UTC
Exact Kernel version: 2.5.47-ac3

Distribution: Red Hat Rawhide

Hardware Environment:  Gigabyte GA -7VAX http://www.giga-byte.com/products/7vax.htm

Northbridge : VIA KT400
Southbridge : VIA 8235
latest bios
hda : IBM-DJNA-371350, ATA DISK drive
hdc : MAXTOR 6L080J4, ATA DISK drive

dmesg declares them as :

hda: 26520480 sectors (13578 MB) w/1966KiB Cache, CHS=1650/255/63
hdc: 156355584 sectors (80054 MB) w/1819KiB Cache, CHS=155114/16/63, UDMA(133)
hdb: ATAPI 40X CD-ROM CD-R/RW drive, 8192kB Cache, UDMA(25)
hdd: ATAPI 40X DVD-ROM drive, 256kB Cache, UDMA(33)

Which seems to inply there is no dma on hda. However thi disk is perfectly dma
capable, as evidenced by :

[root@rousalka root]# /sbin/hdparm -iI /dev/hda


 Model=IBM-DJNA-371350, FwRev=J76OA30K, SerialNo=GM0GMHP0111
 Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
 RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=34
 BuffType=DualPortCache, BuffSize=1966kB, MaxMultSect=16, MultSect=off
 CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=26520480
 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 WriteCache=enabled
 Drive conforms to: ATA/ATAPI-4 T13 1153D revision 17:  1 2 3 4

ATA device, with non-removable media
        Model Number:       IBM-DJNA-371350
        Serial Number:      GM0GMHP0111
        Firmware Revision:  J76OA30K
        Used: ATA/ATAPI-4 T13 1153D revision 17
        Supported: 4 3 2 1 & some of 5
        Logical         max     current
        cylinders       16383   16383
        heads           16      16
        sectors/track   63      63
        CHS current addressable sectors:   16514064
        LBA    user addressable sectors:   26520480
        device size with M = 1024*1024:       12949 MBytes
        device size with M = 1000*1000:       13578 MBytes (13 GB)
        LBA, IORDY(can be disabled)
        Buffer size: 1966.0kB   bytes avail on r/w long: 34     Queue depth: 32
        Standby timer values: spec'd by Standard, no device specific minimum
        R/W multiple sector transfer: Max = 16  Current = 0
        DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 *udma4
             Cycle time: min=120ns recommended=120ns
        PIO: pio0 pio1 pio2 pio3 pio4
             Cycle time: no flow control=240ns  IORDY flow control=120ns
        Enabled Supported:
           *    NOP cmd
           *    READ BUFFER cmd
           *    WRITE BUFFER cmd
           *    Host Protected Area feature set
                Release interrupt
           *    Look-ahead
           *    Write cache
           *    Power Management feature set
                Security Mode feature set
                SMART feature set
                Address Offset Reserved Area Boot
           *    READ/WRITE DMA QUEUED
           *    DOWNLOAD MICROCODE cmd
        not     enabled
        not     locked
        not     frozen
        not     expired: security count
        not     supported: enhanced erase
        18min for SECURITY ERASE UNIT.
Comment 1 Nicolas Mailhot 2002-11-14 12:26:54 UTC
ide -> Alan
Comment 2 Khoa Huynh 2002-11-14 15:32:23 UTC
Bug has owner assigned, moving to Assigned state...
Comment 3 Nicolas Mailhot 2003-01-15 02:16:55 UTC
Still here in 2.5.58
Comment 4 Nicolas Mailhot 2003-02-09 03:38:50 UTC
Still in 2.5.59-bk2
Comment 5 Nicolas Mailhot 2003-02-26 12:58:24 UTC
Still in 2.5.63-bk2
Comment 6 Alan 2003-02-26 14:04:07 UTC
Having looked into this a fait bit I dont think this is actually a bug. Our
behaviour is not to enable DMA on a device the BIOS has chosen to exclude from
DMA. We work on the basis the BIOS has a reason for this. 

Really this one wants to go toVojtech however
Comment 7 Nicolas Mailhot 2003-02-26 14:46:10 UTC
The bios has ne special restriction on this drive (checked bios screens) and it
thinks its an LBA ATA66 just like the second HD is detected as CHS ATA133
(tortured pause key to get the bios startup summary)

BTW 2.4 behaviour is consistent with 2.5 as of kernel-2.4.20-2.54 (RH Raw Hide)
Comment 8 Alan 2003-03-06 13:25:34 UTC
The only reason I can find the code would decide to do this is if the bios has
chosen not to enable DMA on that drive. If it was blacklisted then -d1 wouild
also fail.

Comment 9 Nicolas Mailhot 2003-03-06 13:59:58 UTC
Well, right now I'm wondering if this is not purely a dmesg bug. I see in proc
for hda/settings :

name                    value           min             max             mode
----                    -----           ---             ---             ----
using_dma               1               0               1               rw

So is UDMA enabled or not ?

Another thing is that this drive is leftover from a previous computer, so it
might not like the way modern setup is done.
Comment 10 Nicolas Mailhot 2003-03-06 14:09:03 UTC
The little table summary one gets after bios setup just before it tries to load
systems says :

LBA, ATA66 13579MB
CHS, ATA133 80 GB

so the bios do recognize hda as an ata66 drive
Comment 11 Alan 2003-03-06 15:10:18 UTC
It may be recognizing it as ata66 capable but it really seems to be passing the
kernel a
drive that is marked as pio
Comment 12 Nicolas Mailhot 2003-03-06 15:42:19 UTC
But don't these dmesg lines means the bios passes everything as UDMA ?

    ide0: BM-DMA at 0xdc00-0xdc07, BIOS settings: hda:DMA, hdb:DMA
    ide1: BM-DMA at 0xdc08-0xdc0f, BIOS settings: hdc:DMA, hdd:DMA

(I seem to remember that once upon a time when I had non UDMA devices they were
declared as PIO here)
Comment 13 Nicolas Mailhot 2003-03-06 15:44:02 UTC
Created attachment 199 [details]
Comment 14 Nicolas Mailhot 2003-03-06 15:45:02 UTC
Created attachment 200 [details]
Comment 15 Nicolas Mailhot 2003-03-06 15:46:10 UTC
Created attachment 201 [details]
/sbin/hdparm -iI /dev/hda
Comment 16 Nicolas Mailhot 2003-03-06 15:50:50 UTC
Created attachment 202 [details]
Kernel config
Comment 17 Nicolas Mailhot 2003-03-06 15:53:02 UTC
[root@rousalka nim]# /sbin/hdparm -d1 /dev/hda
 setting using_dma to 1 (on)
 using_dma    =  1 (on)

No blacklisting it seems.
Comment 18 Nishanth Aravamudan 2005-06-25 11:02:12 UTC
Can this bug be closed? Past two years with no activity.

Comment 19 Nicolas Mailhot 2005-06-25 11:52:49 UTC
well, dmesg still says this drive has no dma, and at this point I'm ready to
accept the drive will die before this is fixed, so do as you wish.
Comment 20 Nicolas Mailhot 2005-12-11 03:09:26 UTC
Closing since the hard drive finaly died and is no longer available for testing

Note You need to log in before you can comment on or make changes to this bug.