Bug 80689

Summary: kernel gives bogus "hda: DMA disabled" message.
Product: [Retired] Red Hat Linux Reporter: Hans de Goede <hdegoede>
Component: kernelAssignee: Arjan van de Ven <arjanv>
Status: CLOSED UPSTREAM QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 9CC: wtogami
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-06-05 13:36:23 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Hans de Goede 2002-12-29 22:18:33 UTC
kernel gives a bogus "hda: DMA disabled" message. I noticed that the 2.4.20-2.2
kernel gives a bogus hda: DMA disabled message, while it is actually enabled,
some scanning of the source found me this: in drivers/ide/ide.c
if (drive->autotune != 2) {
                /* DMA timings and setup moved to ide-probe.c */
                if (!driver->supports_dma && HWIF(drive)->ide_dma_off_quietly)
//                      HWIF(drive)->ide_dma_off_quietly(drive);
                        HWIF(drive)->ide_dma_off(drive);
                drive->dsc_overlap = (drive->next != drive && driver->supports_
                drive->nice1 = 1;
        }

Look at how for some reason a dma_off_quietly was changed into a dma_off without
beign quiet. Also notice that the code only checks for the availabality of
dma_off_quietly. I think this should be changed back otherwise you'll get lots
of support calls: why is my dma disabled???

Comment 1 Bill Nottingham 2003-01-01 06:01:10 UTC
It actually is disabled when you get that message. There's just no message when
it reenables it.

Comment 2 Hans de Goede 2003-01-01 09:47:16 UTC
I know (after reading the source) but since Joe the average user doesn't read
kernel source does he know?


Comment 3 Alan Cox 2003-06-05 13:36:23 UTC
This is fixed in the base code now