Bugzilla Bug 209786

After some hours of uptime I can find this in dmesg and dma of my harddrive is
switched off:
...
hda: irq timeout: status=0xd0 { Busy }
hda: irq timeout: status=0xd0 { Busy }
hda: status timeout: status=0xd0 { Busy }
hda: DMA disabled
...

I can switch it back with hdparm -d1 /dev/hda, but after some hours the same
thing happens.

Reproducible: Always

Steps to Reproduce:
1.Kernel 2.6.24-gentoo, 2.6.24-gentoo-r1, 2.6.24-gentoo-r2 with atiixp ide
2.wait for some hours
3.look in dmesg

Actual Results:  
in dmesg:
hda: irq timeout: status=0xd0 { Busy }
hda: irq timeout: status=0xd0 { Busy }
hda: status timeout: status=0xd0 { Busy }
hda: DMA disabled

Expected Results:  
with kernel 2.6.23-gentoo it works without problems

Hardware is Acer Aspire 5021, lspci:
00:00.0 Host bridge: ATI Technologies Inc RS480 Host Bridge (rev 01)
...
00:14.1 IDE interface: ATI Technologies Inc Standard Dual Channel PCI IDE
Controller
...

dmesg:
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ATIIXP: IDE controller (0x1002:0x4376 rev 0x00) at  PCI slot 0000:00:14.1
ACPI: PCI Interrupt 0000:00:14.1[A] -> GSI 16 (level, low) -> IRQ 16
ATIIXP: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0x8410-0x8417, BIOS settings: hda:DMA, hdb:pio
    ide1: BM-DMA at 0x8418-0x841f, BIOS settings: hdc:DMA, hdd:pio
Probing IDE interface ide0...
Switched to high resolution mode on CPU 0
hda: ST9160821A, ATA DISK drive
hda: host max PIO4 wanted PIO255(auto-tune) selected PIO4
hda: UDMA/100 mode selected
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...


and I use ATA/ATPI/MFM/RLL > ATI IXP chipset IDE support, not the Parallel ATA

Please file this as an upstream bug at http://bugzilla.kernel.org
Attach full dmesg output and "lspci -v" output

also please post the new bug URL here when done

(In reply to comment #2)
> also please post the new bug URL here when done

http://bugzilla.kernel.org/show_bug.cgi?id=9994

reported as fixed in 2.6.27 on upstream bug