search for: dma_timer_expiry

...upt >hda: lost interrupt >hda: lost interrupt >hda: set_multmode: status=0x41 { DriveReady Error } >hda: set_multmode: error=0x04 { DriveStatusError} >ide: failed opceode was: 0xef >hda: lost interrupt >hda: lost interrupt >hda: cache flushes supported > hda:<4>hda: dma_timer_expiry: dma status == 0x24 >hda: DMA interript recovery >hda: lost interrupt > hda1 hda2 hda3 >Done. >Begin: Mounting root file system... ... >Begin: Running /scripts/local-top ... >Done. >Begin: Waiting for root file system... ... >hda: dma_timer_expiry: dma status == 0x24 >...

...0.00 2.60 1.81 0.00 95.52 04:50:01 AM all 0.08 0.00 0.79 1.44 0.00 97.69 On one of the guests running Centos 4.6 the impact is so bad I get DMA timeout errors in the syslog, and occasional kernel panics. Mar 11 04:05:04 localhost kernel: hda: dma_timer_expiry: dma status == 0x21 Mar 11 04:05:14 localhost kernel: hda: DMA timeout error Mar 11 04:05:14 localhost kernel: hda: dma timeout error: status=0x50 { DriveReady SeekComplete } Mar 11 04:05:14 localhost kernel: Mar 11 04:05:14 localhost kernel: ide: failed opcode was: unknown Mar 11 04:05:59 localhos...

Hi, I get the below from dmesg. The server seems to run fine, but it does worry me. What should I do? Other than take a backup.. :-) hda: dma_timer_expiry: dma status == 0x21 hda: DMA timeout error hda: dma timeout error: status=0xd0 { Busy } ide: failed opcode was: unknown hda: DMA disabled ide0: reset: success hda: dma_timer_expiry: dma status == 0x21 hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } hda: dma_intr: error=0x40 { Uncorrec...

I''ve been following unstable day to day with mercurial but I''m still having a problem with my HVM testing. I using the i686 Centos + Bluecurve isntaller and I get the following error in the guest during disk formatting: <4>hda: dma_timer_expiry: dma status == 0x21 <4>hda: DMA timeout error <4>hda: dma timeout error: status=0x58 { DriveReady SeekComplete DataRequest } <4> <4>ide: failed opcode was: unknown Not sure if there is a solution to this at present, or if some patches are still coming down the road. -Mik...

We have an old 3.x server whose hd is dying (kernel: hda: dma_timer_expiry: dma status == 0x61) and accessing certain files just crashes the system with a reboot. We have moved as many files to a nfs server as we could so simply. The system has been heavily modified (all using rpms) from baseline. What is the most practical method to replace the hard drive? -Jason Pye...

Hi, I have a EPIA mini-itx board that I have been running Fedora 4 on. I want to install CentOS 4.4 on it since FC4 is no longer supported. The install goes fine but when I reboot the machine after the install I get errors like the following: hda:<4>hda: dma_timer_Expiry : dma status == 0x21 There are other errors about not being able to access the disk and eventually the kernel panics. The disk is a 4 gig compact flash. I used a 1 gig chip for FC4 so I know the thing will run from a flash chip. Does anyone have any idea how to get this to work? Is there a way t...

...new kernel for CentOS 5.3? Till today, my server works without any problems. But after updating to the new kernel 2.6.18-128.7.1.el5 the system freezes completely with no more access by keyboard or over network. The last message in /var/log/messages is 'Aug 25 14:07:41 weidenwinde kernel: hdg: dma_timer_expiry: dma status == 0x21'. I have not change my hardware, have not change configuration and till this new kernel the system was running without any problems. The harddisks are younger than a year. Is someone else this seeing? regards Olaf

...running on a Dell PE 2950 servers. On a HVM/VMX guest also running CentOS 4.3 with the configuration below, we see occasional DMA messages in the guests dmesg output, they don't occur often and for no obvious reason - it seems they normally occur when the load on the host system is low.   hda: dma_timer_expiry: dma status == 0x24 hda: DMA interrupt recovery hda: lost interrupt   Windows 2003 server guests on the same host system don't appear to have any problems (at least none are logged), but two Linux guests do, the above one CentOS and a Fedora core 3 system. Does anyone have any idea how to so...

...283] Apr 11 04:22:29 xenserver kernel: [277113.497288] handlers: Apr 11 04:22:29 xenserver kernel: [277113.497295] [<ffffffffa0099969>] (ahci_interrupt+0x0/0x46b [ahci]) Apr 11 04:22:29 xenserver kernel: [277113.497312] Disabling IRQ #22 Apr 11 04:22:54 xenserver kernel: [277138.645875] hdc: dma_timer_expiry: dma status == 0x64 Apr 11 04:23:00 xenserver kernel: [277145.647409] ata2.00: exception Emask 0x40 SAct 0x0 SErr 0x800 action 0x6 frozen Apr 11 04:23:00 xenserver kernel: [277145.647429] ata2: SError: { HostInt } Apr 11 04:23:00 xenserver kernel: [277145.647438] ata2.00: cmd ea/00:00:00:00:00/0...

...bug.cgi?id=1373 4. [stubdom]The xm save command hangs while saving <Domain-dm>. http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1377 5. [stubdom] cannot restore stubdom based domain. http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1378 6. Live Migration with md5sum running cause dma_timer_expiry error in guest http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1530 7. Very slow mouse/keyboard and no USB thumbdrive detected w/Core i7 & Pvops http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1541 8. Linux guest boots up very slow with SDL rendering http://bugzilla.xensource.com/...

Hi, My xen guest stopped booting suddenly and giving me the below error message. Any idea what is going wrong here? DOM 0 boots OK though. ata5.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 ata5.00: irq_stat 0x40000008 ata5.00: failed command: READ FPDMA QUEUED ata5.00: cmd 60/00:00:cd:ee:36/02:00:09:00:00/40 tag 0 ncq 262144 in res 51/40:72:5b:f0:36/d9:00:09:00:00/40 Emask

Hi, My xen guest stopped booting suddenly and giving me the below error message. Any idea what is going wrong here? DOM 0 boots OK though. ata5.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 ata5.00: irq_stat 0x40000008 ata5.00: failed command: READ FPDMA QUEUED ata5.00: cmd 60/00:00:cd:ee:36/02:00:09:00:00/40 tag 0 ncq 262144 in res 51/40:72:5b:f0:36/d9:00:09:00:00/40 Emask