search for: host_stat

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

One of my CentOS boxes has started giving me errors. The box is CentOS-4.4 (i386) fully updated. It has a pair of SATA drives in a software raid 1 configuration. The errors I see are: ata1: command 0xca timeout, stat 0x50 host_stat 0x24 ata1: status=0x50 { DriveReady SeekComplete } Info fld=0x1e22b8, Current sda: sense key No Sense ata2: command 0xca timeout, stat 0x50 host_stat 0x24 ata2: status=0x50 { DriveReady SeekComplete } Info fld=0x1e2598, Current sdb: sense key No Sense If it was just coming from...

...sive applications, with no problems. Now, I can start dom0 and guest domains with no problem, and they run fine as long as they don''t try to do a lot. But as soon as they get busy - say, compiling something - the console shows an endless stream of: ata1: command 0x35 timeout, stat 0x50 host_stat 0x64 ata2: command 0x25 timeout, stat 0x50 host_stat 0x64 ata4: command 0x35 timeout, stat 0x50 host_stat 0x4 And the system stops responding, until I reset the server or throw it out the window (well, not yet, but it''s coming). I''ve seen posts saying that these errors are rel...

...) | | | | |(4,5,6)| ---------------------------------------------------------------------- Failures: 1. 32bit UP guest fail ltp gettimeofday02: "Time is going backwards" 2. 32bit UP guest hangs under load: "ata1: command 0x25 timeout, stat 0x50 host_stat 0x64" 3. 32bit UP guest crashed during user load test: "(XEN) Couldn''t alloc shadow page! dom1 count=952" 4. 64bit SMP 2 CPU guest hangs under load: "ata1: command 0x25 timeout, stat 0x50 host_stat 0x64" 5. 64bit SMP guest report these messages whil...

...ertain machines, I''m experiencing the following problem, after a while, I get this error in dom0''s dmesg: TA: abnormal status 0xD0 on port 0xD080EC87 ATA: abnormal status 0xD0 on port 0xD080EC87 ATA: abnormal status 0xD0 on port 0xD080EC87 ata1: command 0x35 timeout, stat 0x51 host_stat 0x61 ata1: status=0x51 { DriveReady SeekComplete Error } ata1: error=0x04 { DriveStatusError } SCSI error : <0 0 0 0> return code = 0x8000002 sda: Current: sense key=0xb ASC=0x0 ASCQ=0x0 end_request: I/O error, dev sda, sector 449410141 also in dom0''s /var/log/messages, I have thi...

...machine), it is good. But, where some of them have high traffic and thus require high disk usage i get this error in dom0''s dmesg: ATA: abnormal status 0xD0 on port 0x9F7 ATA: abnormal status 0xD0 on port 0x9F7 ATA: abnormal status 0xD0 on port 0x9F7 ata1: command 0x35 timeout, stat 0xd0 host_stat 0x20 ata1: translated ATA stat/err 0xd0/00 to SCSI SK/ASC/ASCQ 0xb/47/00 ata1: status=0xd0 { Busy } sd 0:0:0:0: SCSI error: return code = 0x8000002 sda: Current: sense key: Aborted Command Additional sense: Scsi parity error end_request: I/O error, dev sda, sector 118401022 And the filesystem...