Dma Timeout Error Status=0x58 Driveready Seekcomplete Datarequest

Wiki Search Tutorials/Articles Search HCL Search Reviews Search ISOs Go to Page... LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware Hard Drive Problems: timeout waiting for DMA; error waiting for DMA User Name Remember Me? Password Linux - Hardware This forum is for Hardware issues. Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux? Notices Welcome to LinuxQuestions.org, a friendly and active Linux Community. You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today! Note that registered members see fewer ads, and ContentLink is completely disabled once you log in. Are you new to LinuxQuestions.org? Visit the following links: Site Howto | Site FAQ | Sitemap | Register Now If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here. Having a problem logging in? Please visit this page to clear all LQ-related cookies. Introduction to Linux - A Hands on Guide This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter. For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own. Click Here to receive this Complete Guide absolutely free. Search this Thread 11-03-2003, 02:34 PM #1 mintee LQ Newbie Registered: Nov 2003 Location: Philly Distribution: slack Posts: 2 Rep: Hard Drive Problems: timeout waiting for DMA; error waiting for DMA Ok, I've driven myself sick with this problem. Been living off google answers for the past 4 days, with no help. First I describe the problems, then at the end I show my dmesg and lspci -vvv. I have a AMD Athlon 700, on some mobo, donno, don't matter. Currently I have 1 20GB HD as boot drive, and 6 120GB made into a software RAID5, using 2.4.22 kernel, self-compiled. Earlier I was using a 2.4.20 self-compile kernel (same hardware) and there was never a

Sat, 3 Jul 2004 14:02:57 -0400 Message-id: <[🔎]20040703180257.GA30885@nerdnetworks.org> 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 http://www.linuxquestions.org/questions/linux-hardware-18/hard-drive-problems-timeout-waiting-for-dma%3B-error-waiting-for-dma-111942/ 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 https://lists.debian.org/debian-user/2004/07/msg00345.html 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) kee

DMA timeout and other boot problems If this is your first visit, be sure to check out the FAQ by clicking the link above. You may http://forums.justlinux.com/showthread.php?128412-DMA-timeout-and-other-boot-problems have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. Results 1 http://linux.kernel.narkive.com/MbFHHZv7/dma-timeout-error to 5 of 5 Thread: DMA timeout and other boot problems Tweet Thread Tools Show Printable Version Email this Page… Subscribe to this Thread… Display Linear Mode Switch to Hybrid Mode Switch dma timeout to Threaded Mode 05-30-2004,12:53 AM #1 owlish View Profile View Forum Posts Registered User Join Date Feb 2004 Posts 29 DMA timeout and other boot problems My boot time is terrible but the distro works fine. I am using gentoo. I am facing some dma problems in both gentoo and winxp so I guess its a problem with my hdd. What I need to know dma timeout error is how can I disable dma during boot time? I understand that I need to recompile the kernel but I dont know what settings I need to change. I have attached my kernel config so can anyone please take a look and tell me what I need to change (and any recommendations on better optimizations ;) ) dmesg Linux version 2.6.6-rc1 (root@zi0n) (gcc version 3.2.3 20030422 (Gentoo Linux 1.4 3.2.3-r1, propolice)) #1 Fri May 14 01:11:39 EDT 2004 BIOS-provided physical RAM map: BIOS-e820: 0000000000000000 - 000000000009fc00 (usable) BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved) BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved) BIOS-e820: 0000000000100000 - 000000001dff0000 (usable) BIOS-e820: 000000001dff0000 - 000000001dff3000 (ACPI NVS) BIOS-e820: 000000001dff3000 - 000000001e000000 (ACPI data) BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved) 479MB LOWMEM available. On node 0 totalpages: 122864 DMA zone: 4096 pages, LIFO batch:1 Normal zone: 118768 pages, LIFO batch:16 HighMem zone: 0 pages, LIFO batch:1 DMI 2.2 present. ACPI: RSDP (v000 VIAP4X ) @ 0x000f68e0 ACPI: RSDT (v001 VIAP4X AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x1dff3000 ACPI: FADT (v001 VIAP4X AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x1dff3040 ACPI: DSDT (v001 VIAP4X AWRDACPI 0x00001000 MSFT 0x0100000d) @ 0x00000000 Built 1 zonelists Kernel command li

boot:hdb: dma_timer_expiry: dma status == 0x41hdb: DMA timeout errorhdb: dma timeout error: status=0x58 { DriveReady SeekComplete DataRequest }hdb: status error: status=0x58 { DriveReady SeekComplete DataRequest }hdb: drive not ready for commandhdb: dma_timer_expiry: dma status == 0x41hdb: DMA timeout errorhdb: dma timeout error: status=0x58 { DriveReady SeekComplete DataRequest }hdb: status error: status=0x58 { DriveReady SeekComplete DataRequest }hdb: drive not ready for commandAny ideas?Thanks,A.-To unsubscribe from this list: send the line "unsubscribe linux-kernel" inthe body of a message to ***@vger.kernel.orgMore majordomo info at http://vger.kernel.org/majordomo-info.htmlPlease read the FAQ at http://www.tux.org/lkml/ Bartlomiej Zolnierkiewicz 2004-10-02 16:50:11 UTC PermalinkRaw Message Post by Adam ShermanI have a VIA M6000 board with an ATA CompactFlash adaptor containing a512MB SanDisk card.hdb: dma_timer_expiry: dma status == 0x41hdb: DMA timeout errorhdb: dma timeout error: status=0x58 { DriveReady SeekComplete DataRequest }hdb: status error: status=0x58 { DriveReady SeekComplete DataRequest }hdb: drive not ready for commandhdb: dma_timer_expiry: dma status == 0x41hdb: DMA timeout errorhdb: dma timeout error: status=0x58 { DriveReady SeekComplete DataRequest }hdb: status error: status=0x58 { DriveReady SeekComplete DataRequest }hdb: drive not ready for commandAny ideas?If this is a new CF capable of DMA but CF-to-IDE adapter doesn't supportDMA (most don't) then "ide=nodma" kernel command line parameter shoulddo the job. It might be also bug in via82cxxx host driver.Maybe DMA should be off by default for CF but it requires fixing almostevery IDE host driver and why punish good hardware.-To unsubscribe from this list: send the line "unsubscribe linux-kernel" inthe body of a message to ***@vger.kernel.orgMore majordomo info at http://vger.kernel.org/majordomo-info.htmlPlease read the FAQ at http://www.tux.org/lkml/ Adam Sherman 2004-10-02 17:40:08 UTC PermalinkRaw Message Post by Bartlomiej ZolnierkiewiczPost by Adam ShermanI have a VIA M6000 board with an ATA CompactFlash adaptor containing a512MB SanDisk card.hdb: dma_timer_expiry: dma status == 0x41hdb: DMA timeout errorhdb: dma timeout error: status=0x58 { DriveReady SeekComplete DataRequest }If this is a new CF capable of DMA but CF-to-IDE adapter doesn't supportDMA (most don't) then "ide=nodma" kernel command line parameter shoulddo the job. It might be also bug in via8