search for: dma_timer_expiri

Hello list, I have a problem with my new xen server wich can''t reach to start my linux hardware virtual machines which works on my old server without modifications. Here is my situation : On all xen servers (3), I use xen 3.2 for a Dom0 compiled with the linux kernel caming from http://xenbits.xensource.com/linux-2.6.18-xen.hg My 2 old xen servers are : Dual core Intel(R) Pentium(R) D

Is anyone else having major I/O peaks due to logrotate or other jobs running simultaneously across multiple guests. I have one KVM server running Centos 5.4 with local disk that is seriously suffering as most of the guests rotate their syslog at the same time. Looking at the KVM server I'm seeing 11:00:01 PM CPU %user %nice %system %iowait %steal %idle 03:40:01 AM

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

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

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 Pyeron

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.

Hello, is there a known problem with the 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

Hi,   We've deployed Xen 3.0.2-2 successfully on a CentOS 4.3 installation 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

Hello, I have experienced a dom0 crash where the system became unreachable via the network and the console was unresponsive. I would appreciate help interpretting the logs and any configuration change suggestions. It is a stock Debian Lenny dom0 running xen 3.2.1 with kernel 2.6.26-2-xen-amd64 and an AMD Athlon IIx4 with 4 GB of RAM. It is running 4 VMs. One VM has two PCI NICs being

Hi all, This is our bi-weekly test report for Xen-unstable tree. There are 6 new bug found in this two weeks. And there are 3 bugs had fixed in past two weeks. We use Pv_ops(xen/stable-2.6.32.x) as Dom0 in our testing. Status Summary ==================================================================== Feature Result

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