Bug 15
| Summary: | No dma on first hard drive | ||
|---|---|---|---|
| Product: | IO/Storage | Reporter: | Nicolas Mailhot (Nicolas.Mailhot) |
| Component: | IDE | Assignee: | Alan (alan) |
| Status: | REJECTED UNREPRODUCIBLE | ||
| Severity: | normal | CC: | nacc |
| Priority: | P2 | ||
| Hardware: | IA-32 | ||
| OS: | Linux | ||
| Kernel Version: | 2.5.47-ac3 to 2.5.73 | Subsystem: | |
| Regression: | --- | Bisected commit-id: | |
| Attachments: |
dmesg
lspci /sbin/hdparm -iI /dev/hda Kernel config |
||
|
Description
Nicolas Mailhot
2002-11-14 12:25:44 UTC
ide -> Alan Bug has owner assigned, moving to Assigned state... Still here in 2.5.58 Still in 2.5.59-bk2 Still in 2.5.63-bk2 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 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) 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. 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. The little table summary one gets after bios setup just before it tries to load systems says : LBA, ATA66 13579MB CDRW, UDMA 1 CHS, ATA133 80 GB DVD, ATA 33 so the bios do recognize hda as an ata66 drive It may be recognizing it as ata66 capable but it really seems to be passing the kernel a drive that is marked as pio 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)
Created attachment 199 [details]
dmesg
Created attachment 200 [details]
lspci
Created attachment 201 [details]
/sbin/hdparm -iI /dev/hda
Created attachment 202 [details]
Kernel config
[root@rousalka nim]# /sbin/hdparm -d1 /dev/hda /dev/hda: setting using_dma to 1 (on) using_dma = 1 (on) No blacklisting it seems. Can this bug be closed? Past two years with no activity. Thanks, Nish 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. Closing since the hard drive finaly died and is no longer available for testing |