similar to: task md1_resync:9770 blocked for more than 120 seconds and OOM errors

I've been experiencing delays access data off my file server since I upgraded to 5.3... either I hosed something, have bad hardware or very unlikely, found a bug. When reading or writing data, the stream to the hdd's stops every 5-10 min and %iowait goes through the roof. I checked the logs and they are filled with this diagnostic data that I can't readily decipher. my setup

CentOS Community, Would someone who is familiar with reading boot messages and kernel errors be able to assist with advising me on what the following errors might mean in dmesg. It seems to come up randomly towards the end of the logfile. ------------[ cut here ]------------ WARNING: at arch/x86/kernel/cpu/mtrr/generic.c:467 generic_get_mtrr+0x11e/0x140() (Not tainted) Hardware name: empty

We have a 3TB external USB drive that I am trying to attach to some CentOS5 servers. I have tried an older Dell PE1950 and a newer R310 but neither one seems to be able to read the drive. It works no problem on windows servers/workstations and I was able to format with NTFS. I know there are different methods for formatting large disks but this one doesn't even seem to show up as a /dev/

Hi, A problem with EVMS and Xen: I have patched a 2.6 kernel with the evms patches and then with the Xen patched, compiled and installed it. (kernel is 2.6.11.9 - which is what this server has been running for the past few months w/o the evms patches) At first everything seems to work just fine, I am able to use evms to create a new "volume", in this case it is based on MD/RAID-5 but

We've just started getting this. We're running 5.10, kernel 2.6.32-358.18.1.el6.x86_64. Anyone else seen anything like this, or have any ideas? mark Nov 1 14:34:21 <server> kernel: WARNING: at block/ll_rw_blk.c:543 blk_do_ordered() Nov 1 14:34:21 <server> kernel: Nov 1 14:34:21 <server> kernel: Call Trace: Nov 1 14:34:22 <server> kernel:

I accidentally noticed this error written to the warn log on my Dell R200's when the machines booted up after latest kernel update. Google doesn't have this exact error, only a few with differently named devices, but all seem to have to do with USB. Could this be a bug? Didn't see this error on other machines with more than one USB port, though. Jun 26 22:59:07 c4 kernel:

I am getting this message quite often lately. Centos 5.3, AMD dual core 5050e system x64 1 GIG ram, 4 GIG swap I dont have that much running that the kernel should be cutting out my processes. Any thoughts? Jerry ------------ emTotal: 766264 kB MemFree: 583984 kB Buffers: 9572 kB Cached: 31004 kB SwapCached: 36280 kB Active: 20240 kB Inactive:

Hi Every time I up a VM with Xen 3.0.3 on CentOS 5.4 I get this messages on kernel: Apr 5 09:03:07 zebra kernel: BUG: warning at lib/kref.c:32/kref_get() (Not tainted) Apr 5 09:03:07 zebra kernel: Apr 5 09:03:07 zebra kernel: Call Trace: Apr 5 09:03:07 zebra kernel: [<ffffffff8023824d>] kref_get+0x38/0x3d Apr 5 09:03:07 zebra kernel: [<ffffffff8025a440>] kobject_get+0x12/0x17

Hi. I have a RHEL server that has some errors in dmesg , what do they mean, how do I fix them ? mtrr: type mismatch for f9000000,800000 old: write-back new: write-combining mtrr: type mismatch for f9000000,1000000 old: write-back new: write-combining mtrr: type mismatch for f9fe0000,10000 old: write-back new: write-combining mtrr: type mismatch for f9fc0000,20000 old: write-back new:

Hi, When I tested pvfb, I got the following warnings. It seems to be caused by checking/setting info->dirty without dirty_lock. We need to check/set info->dirty safely. xenfb_update_screen bogus rect 2147483647 0 2147483647 0 BUG: warning at /root/linux-2.6.18-xen.hg/drivers/xen/fbfront/xenfb.c:240/xenfb_update_screen() Call Trace: [<ffffffff8036920e>] xenfb_thread+0x19b/0x2be

Hello, On a VM guest (running under KVM) with CentOS 5.8, I yesterday strangely got the following (see below). The server runs apache/php/squirrelmail/postfix/dovecot/openldap and it is a production server. Do you advise to do some particular file system checks or other settings? Any other advice? Such errors have not appeared in the past. Thanks, Nick System info:

Hello, I''m running into some trouble with what appear on the surface to be OOM issues in Dom0, but I''m not seeing any other evidence. This typically happens during periods of high I/O, and has occurred during RAID initial sync, and mkfs.ext4ing (as a test, no intention to keep ext4 on this array). I''ve found some older posts citing very similar circumstances, however

Hi! I tried to pcipassthrough usb-controllers to domu to use it with a memory-stick. First xen complained that the driver needs write-access to its configuration space, so I added these to pci-quirks. Since it still didn''t work I also added the device to pci-permissive but I still get an errormessage with Oops (at the end of this email) when sticking in the memory-stick. I tried

Hi! I tried to pcipassthrough usb-controllers to domu to use it with a memory-stick. First xen complained that the driver needs write-access to its configuration space, so I added these to pci-quirks. Since it still didn''t work I also added the device to pci-permissive but I still get an errormessage with Oops (at the end of this email) when sticking in the memory-stick. I tried

Hi list, We are experiencing a memory leak on our SquirrelMail server since the 5.3 update. The server is fully updated, only stock rpms. The httpd processes are eating all the memory and after swapping like hell, the server became unresponsive and we must hard-reboot it. The server is not that much loaded (max 10-15 concurrent users but with tons of mail in their inbox). Configuration's

I have a single VM (of 11) that has a recurring problem. This image has moved from machine to machine, with the problem following it. This image has been rebuilt from scratch, and the problem recurred. It would appear that there is something in the behaviour of this VM which causes it to crash and causes Xend to become unhappy. The problem presents as: Domain crashes, becomes zombie. xm

An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20100405/b0bb4b91/attachment-0003.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: GilbertoNunesFerreira_html_185aa38c.jpg Type: image/jpeg Size: 16538 bytes Desc: not available URL:

Hi, i''m prepering to upgrade my servers from xen 3.0.3 32-bit to 3.2.1 64-bit. The old system: Debian 4.0 i386 with included hypervisor 3.0.3 (pae) and dom0 kernel. The new systen: Debian lenny amd64 with the included hypervisor 3.2.1 and dom0 kernel from Debian 4.0 amd64. My domUs have a self compiled kernel out of the dom0 kernel of the old system (mainly the dom0 kernel but

We have a (supposedly) quite standard setup: 2 Dom0 with drbd-on-lvm and a bunch of DomU, on Quad Xeon Dell servers. We tried with both sid-based and etch-based (+ 3.1 xen hypervisor and drbd 8 from backports.org ) Dom0, and quite consistently have "kernel: invalid opcode: 0000 [1] SMP" errors which freezes Dom0 (during lasts tests a simple start-and-stop loop of 10 DomU can trigger

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