Hide Forgot
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225 Description of problem: This looks to me like a kernel issue, but I'm giving it to youse guys rather than pester the kernel people directly. I recently installed a second disk on my system, which had been performing flawlessly. Now I get a variety of disk errors. The second disk is virtually identical to the first, except that it supports more DMA standards, and is 40 Gb bigger. I sent it back to the retailer and replaced it with an identical model, and I continue to get the same errors, but only when this second disk is installed, and whether it is installed as hda or hdc. I will attach detailed information about the disk and controller, and the specific errors I've seen. Version-Release number of selected component (if applicable): kernel-2.4.20-13.9 How reproducible: Always Steps to Reproduce: 1. Unfortunately, I would think you'd need to duplicate my hardware setup to reproduce the bug. Additional info:
Created attachment 91946 [details] More information about disks, controller, and errors
One more thing about the two disks: May 24 20:56:54 localhost kernel: hda: 160836480 sectors (82348 MB) w/1863KiB Cache, CHS=10011/255/63, UDMA(33) May 24 20:56:54 localhost kernel: hdc: 241254720 sectors (123522 MB) w/1821KiB Cache, CHS=15017/255/63, UDMA(100)
I have the same problem with kernel 2.4.20-18.7 (under RH7.3). The IDE controller is a: 00:07.1 IDE interface: Intel Corp. 82371SB PIIX3 IDE [Natoma/Triton II] The errors: hdc: dma_timer_expiry: dma status == 0x60 hdc: timeout waiting for DMA hdc: timeout waiting for DMA hdc: (__ide_dma_test_irq) called while not waiting hdc: status error: status=0x58 { DriveReady SeekComplete DataRequest } hdc: drive not ready for command hdc: status timeout: status=0xd0 { Busy } Still during bootup, DMA will get disabled by the kernel: hdc: DMA disabled This is true for all four IDE drives that I have in the machine, DMA gets disabled for all of them. This used to work under 2.4.18-27.7.x, no DMA problems at all. I tried 2.4.21, too, it shows exactly the same behavior as 2.4.20-18.7. Regards, Marc
Thanks for the bug report. However, Red Hat no longer maintains this version of the product. Please upgrade to the latest version and open a new bug if the problem persists. The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, and if you believe this bug is interesting to them, please report the problem in the bug tracker at: http://bugzilla.fedora.us/