Dma Timeout Error Linux

piCore-8.0 is available! Home Help Login Register Tiny Core Linux » Tiny Core Base » TCB Talk » [SOLVED] hde: timeout waiting for DMA « previous next » Print Pages: [1] 2 3 4 Go Down Author Topic: [SOLVED] hde: timeout waiting for DMA (Read 8902 times) jason.ritzke WikiUser Posts: 20 [SOLVED] hde: timeout waiting for DMA « on: January 22, 2011, 10:08:46 AM » Alright, I've tried this with every cheat code I know from other distros, in case there is one undocumented. No matter what I do, I cannot get TC to boot. Every time I get:hde: timeout waiting for DMANow, I only have 4 hdd's in this box, so I'm assuming hde is the cd? Also, before you ask, the system cannot boot from a USB stick as an alternative. Compaq Proliant ML330 G2.Any advice would be appreciated. I'm confident that once I get this booting I can move on fairly quickly. « Last Edit: January 25, 2011, 07:52:09 PM by jason.ritzke » Logged curaga Administrator Hero Member Posts: 9212 Re: hde: timeout waiting for DMA « Reply #1 on: January 22, 2011, 10:33:54 AM » Try ide=nodma. Logged The only barriers that can stop you are the ones you create yourself. Rich TinyCore Moderator Hero Member Posts: 5097 Re: hde: timeout waiting for DMA « Reply #2 on: January 22, 2011, 11:01:43 AM » Hi JasonThe fact that it's complaining about hde suggests that you have 5 drives in your rig. Areyou running SCSI, a mix of SCSI and ide, or an extra IDE controller card? A little moreinformation about your hardware might aid in solving your problem. You can also trychecking your BIOS setup to see if you can turn off DMA to your drives. If you can, do itto all drives just to see if you can boot and to make sure none of the other drives arecausing a problem. If it boots you can start re-enabling DMA on the drives one by one. Logged jason.ritzke WikiUser Posts: 20 Re: hde: timeout waiting for DMA « Reply #3 on: January 22, 2011, 04:09:11 PM » Intelligent reply, unfortunately something I've already tried.I have tried (from previous posts for tinycore here and elsewhere):nodma ide-core=nodma ide=nodma dma=offOn to the second reply:Unfortunately, the bios of this system does not allow me to deactivate the DMA on the system, In fact, it doesn't give me many options on the drives themselves at all. It is a compaq server from the early 2000's, which means proprietary and annoying as hell. If I could get it to even boot a *nix distro from the HDD I would, but the system won't boot a kernel from the HDD at all. Logged

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 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 to 5 of 5 Thread: DMA timeout and other boot problems Tweet Thread Tools http://forum.tinycorelinux.net/index.php?topic=8548.0 Show Printable Version Email this Page… Subscribe to this Thread… Display Linear Mode Switch to Hybrid Mode Switch 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 http://forums.justlinux.com/showthread.php?128412-DMA-timeout-and-other-boot-problems 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 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 p

Edit Invalid Medium Unassigned Edit You need to log in to change this bug's status. Affecting: linux (Ubuntu) Filed here by: Fabian Schindler When: 2005-11-20 Completed: 2010-02-04 Target Distribution Baltix https://bugs.launchpad.net/bugs/25975 BOSS Juju Charms Collection Elbuntu Guadalinex Guadalinex Edu Kiwi Linux nUbuntu PLD Linux Tilix tuXlab Ubuntu Ubuntu Linaro Evaluation Build Ubuntu RTM Package (Find…) Project (Find…) Status Importance Invalid Medium Assigned to http://lists.oregonstate.edu/pipermail/linux/2007-March/002150.html Nobody Me Comment on this change (optional) Email me about changes to this bug report Also affects project (?) Also affects distribution/package Nominate for series Bug Description Dualboot system on my Laptop dma timeout (Issam Smartbook i1000c) (one OS being Windows XP SP2.. sorry). Ubuntu 5.10 is installed on the Laptop. From time to time I experience temoprary harddisk freezes or lockups. I checked if the Hitachi 40GB 2,5" hdd might be faulty. Tested the drive with Hitachis system tools from their home page and the drive reported well on all integrity and health checks. I did health checks dma timeout error again with Ubuntu and the harddrive was sane again. No lockups in Windows XP at all. The drive was checked by an IT-expert at University and no problems were found. Everything was sane. But in /var/log/messages, there is this error reported repeatedly: ... Nov 20 15:35:35 localhost kernel: [4294765.104000] hda: dma_timer_expiry: dma status == 0x20 Nov 20 15:35:35 localhost kernel: [4294765.104000] hda: DMA timeout retry Nov 20 15:35:35 localhost kernel: [4294765.104000] hda: status error: status=0x58 { DriveReady SeekComplete DataRequest } Nov 20 15:35:35 localhost kernel: [4294765.104000] Nov 20 15:35:35 localhost kernel: [4294765.104000] ide: failed opcode was: unknown The drive seems to use the UDMA mode. user@kopernikus:~$ sudo hdparm -i /dev/hda /dev/hda: Model=HITACHI_DK23FB-40, FwRev=00M1A0A1, SerialNo=4CY679 Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs } RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4 BuffType=DualPortCache, BuffSize=8192kB, MaxMultSect=16, MultSect=off CurCHS=4047/16/255, CurSects=16511760, LBA=yes, LBAsects=78140160 IORDY=yes, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120} PIO modes: pio0 pio1 pio2 pio3 pio4 DMA modes: mdma0 mdma1 mdma2 UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5 AdvancedPM=yes: mode=0x80 (128) WriteCache=enabled Drive conforms to: ATA/ATAPI-5 T13 1321D revision 3: * signifies the current active mode The drive is NOT nearing death. That was checked already. (I searched bugzilla

] I searched google for "ide: failed opcode was: unknown" and came up with this (along with other useful looking pages): http://lists.centos.org/pipermail/centos/2005-November/056160.html It looks like your same questions with some answers in replies. Cully On 3/12/07, Toshimi Minoura wrote: > Hi, > > At around 17:45 pm on March 10, one of our servers > running Ubuntu failed. I found the entries given below > in /var/log/kern.log. When I tried to reboot the machine, > the same DMA error was reported. > > What kind of error is this? I could read data from the failed (?) disk > on another machine. > > Is the disk controller faulty or the disk itself? > > Thank you in advance for any help. > > Toshi > > ******** > > Mar 8 18:54:46 nagara kernel: [17179611.320000] Bluetooth: RFCOMM socket layer > initialized > Mar 8 18:54:46 nagara kernel: [17179611.320000] Bluetooth: RFCOMM TTY layer > initialized > Mar 8 18:54:46 nagara kernel: [17179611.320000] Bluetooth: RFCOMM ver 1.7 > > (*** Now errors start ***) > > Mar 9 13:34:48 nagara kernel: [17246708.456000] hda: dma_timer_expiry: dma > status == 0x21 > Mar 9 13:34:48 nagara kernel: [17246718.456000] hda: DMA timeout error > Mar 9 13:34:48 nagara kernel: [17246718.456000] hda: dma timeout error: > status=0x58 { DriveRead\y SeekComplete DataRequest } > Mar 9 13:34:48 nagara kernel: [17246718.456000] ide: failed opcode was: unknown > . . . > > Mar 9 13:34:48 nagara kernel: [17246798.572000] hda: dma_timer_expiry: dma > status == 0x21 > Mar 9 13:34:48 nagara kernel: [17246808.572000] hda: DMA timeout error > Mar 9 13:34:48 nagara kernel: [17246808.572000] hda: dma timeout error: > status=0x58 { DriveRead\y SeekComplete DataRequest } > Mar 9 13:34:48 nagara kernel: [17246808.572000] ide: failed opcode was: unknown > > (*** The server failed at 17:45 on March 10. ***) > > (*** Rebooting failed with the error reported above. ****) > > (*** The machine was rebooted with reconstructed mirrored disks. **) > > Mar 10 20:00:21 nagara kernel: Inspecting /boot/System.map-2.6.15-28-386 > Mar 10 20:00:21 nagara kernel: Loaded 23072 symbols from > /boot/System.map-2.6.15-28-386. > Mar 10 20:00:21 nagara kernel: Symbols match kernel version 2.6.15. > > _______________________________________________ > linux mailing list > http://lug.oregonstate.edu/ > http: