dma timeout retry: status=0x58
Hello -
The reason I'm submitting this to the Debian list is because this issue seems to be related to whatever kernel options Debian gives me, or perhaps the specific 2.4 version that Debian installs. In short, when I boot Red Hat 9 on this system, also using a 2.4 kernel, I don't seem to have this problem.
The problem I'm referring to is basically this: on my Dell Latitude LS laptop, when I reboot the system, it is unable to enable dma on its hard drive. However after any power down/power up cycle, it has no problem doing so. The drive is an IBM, and I've used their drive fitness test tool, which tells me the drive is fine. I also installed smartmontools and had it check the S.M.A.R.T. status of the drive, and it checked out as well.
When the system is warm booting, I get these errors when it tries to enable dma (pulled from dmesg so you can see context):
------
Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
PIIX4: IDE controller at PCI slot 00:07.1
PIIX4: chipset revision 1
PIIX4: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xfcd0-0xfcd7, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0xfcd8-0xfcdf, BIOS settings: hdc:pio, hdd:pio
hda: C/H/S=0/0/0 from BIOS ignored
hda: IBM-DJSA-210, ATA DISK drive
blk: queue c0398c60, I/O limit 4095Mb (mask 0xffffffff)
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: attached ide-disk driver.
apm: get_event: Interface not connected
hda: 19640880 sectors (10056 MB) w/384KiB Cache, CHS=19485/16/63, UDMA(33)
Partition check:
hda:<4>hda: dma_timer_expiry: dma status == 0x21
hda: error waiting for DMA
hda: dma timeout retry: status=0x58 { DriveReady SeekComplete DataRequest }
[PTBL] [1222/255/63] hda1 hda2 <<4>hda: dma_timer_expiry: dma status == 0x21
hda: error waiting for DMA
hda: dma timeout retry: status=0x58 { DriveReady SeekComplete DataRequest }
hda5 >
hda: dma_timer_expiry: dma status == 0x21
hda: error waiting for DMA
hda: dma timeout retry: status=0x58 { DriveReady SeekComplete DataRequest }
hda: dma_timer_expiry: dma status == 0x21
hda: error waiting for DMA
hda: dma timeout retry: status=0x58 { DriveReady SeekComplete DataRequest }
------
I get the same errors if I try to manually enable dma with hdparm. If I just check drive status with hdparm, it indicates dma is off:
------
/dev/hda:
multcount = 16 (on)
IO_support = 0 (default 16-bit)
unmaskirq = 0 (off)
using_dma = 0 (off)
keepsettings = 0 (off)
readonly = 0 (off)
readahead = 8 (on)
geometry = 1222/255/63, sectors = 19640880, start = 0
------
On a cold boot, or a simple power down/power up, I don't see these issues:
------
Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
PIIX4: IDE controller at PCI slot 00:07.1
PIIX4: chipset revision 1
PIIX4: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xfcd0-0xfcd7, BIOS settings: hda:pio, hdb:pio
ide1: BM-DMA at 0xfcd8-0xfcdf, BIOS settings: hdc:pio, hdd:pio
hda: C/H/S=0/0/0 from BIOS ignored
hda: IBM-DJSA-210, ATA DISK drive
blk: queue c0398c60, I/O limit 4095Mb (mask 0xffffffff)
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: attached ide-disk driver.
apm: get_event: Interface not connected
hda: 19640880 sectors (10056 MB) w/384KiB Cache, CHS=19485/16/63, UDMA(33)
Partition check:
hda: [PTBL] [1222/255/63] hda1 hda2 < hda5 >
------
------
/dev/hda:
multcount = 16 (on)
IO_support = 0 (default 16-bit)
unmaskirq = 0 (off)
using_dma = 1 (on)
keepsettings = 0 (off)
readonly = 0 (off)
readahead = 8 (on)
geometry = 1222/255/63, sectors = 19640880, start = 0
------
My BIOS doesn't let me choose anything with regard to DMA settings on this drive, so I don't think there's any issue there. And as I said, Red Hat 9 can enable DMA consistently no problem. This seems to indicate some kind of driver or kernel issue, but Google hasn't shown me to an answer yet.
I am running Debian Unstable with the 2.4.26 kernel. Any suggestions about possible solutions to this problem would be greatly appreciated. Thanks in advance,
/Owen
Reply to: