similar to: out of memory

Hello, yesterday night I had a problem with my server located at a hoster (strato.de). I couldn't ssh to it and over the remote serial console I saw "out of memory" errors (sorry, don't have the text). Then I had reinstall CentOS 5.5/64 bit + all my setup (2h work), because I have a contract with a social network and they will shut down my little card game if it is not

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:

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:

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'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

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/

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:

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, 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

Hi, One of my servers has had its dom0 "oops" over and over twice in the last week. Unfortunately this is newly deployed so I have no idea if it is down to Xen or not. xen_changeset : Mon Dec 12 18:47:47 2005 +0100 8270:4ad23e798798 dom0 kernel is a vanilla 2.6.12 with Ralph''s .6+xen kernel patch applied. x86_32 sarge packages were used. The .config is

Hi all, yeah ok don''t laugh at my hardware. I got this.... is it normal to get OOM killers with heavy usage of LVM CoW clones and only 64mb ram assigned to dom0 PIII (also is running apache2/nfs/sshd and 4 idling domU''s) Aug 15 14:40:27 xen5etch kernel: printk: 36 messages suppressed. Aug 15 14:40:30 xen5etch kernel: oom-killer: gfp_mask=0x280d2, order=0 Aug 15 14:40:30

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

(please keep me on Cc when replying) I have a server running Xen that regularly spews the following. The box seems to survive fine regardless - just thought I''d let everyone know. Dec 8 12:19:26 server kernel: 0x47/0x7a Dec 8 12:19:26 server kernel: [alloc_skb_from_cache+70/243] alloc_skb_from_cache+0x46/0xf3 Dec 8 12:19:26 server kernel: [__dev_alloc_skb+70/92]

Hi guys, Another strange behavior with some test servers. They are booted using 2.6.11.12, xen-2.0.6, Debian. The only daemons running on dom0 are : xend, smtp, quagga (ospf), portmap (nfs client), sshd. Memory usage at startup is aroung 30 MB. Dom0 reserved memory is 256 MB. The only things that happen on this server are domU''s start/stop (xm create, xm shutdown) and a

Hi, i''ve a big problem in a xenU (256M RAM, 2.6.11.12-xenU, in 3 LVM partition (/, swap and /home) This xenU freeze and crash with this messages in syslog. This xenU work very fine since 2005 september. Is it serious ? What could be the solution ? Regards Franck ############ SYSLOG ...................... Jun 18 08:45:21 lemodev kernel: oom-killer: gfp_mask=0x1d2 Jun 18 08:45:21

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

On 08/31/2017 07:50 AM, PJ Welsh wrote: > A recently created and fully functional CentOS 7.3 VM fails to boot > after applying CR updates: <snip> > Server OS is CentOS 7.3 using Xen (no CR updates): > rpm -qa xen\* > xen-hypervisor-4.6.3-15.el7.x86_64 > xen-4.6.3-15.el7.x86_64 > xen-licenses-4.6.3-15.el7.x86_64 > xen-libs-4.6.3-15.el7.x86_64 >

Hi - Running into the error below when copying over large files via ssh. This occurs even when I have vm.overcommit_memory=2 set in /etc/sysctl.conf. The research I've done indicates that this is a bio-uses-GFP_DMA bug with EM64T. I'm running CentOS 4.4 with the 2.6.9-42.0.3.ELsmp x86_64 kernel on the following hardware: 2 x Intel Xeon CPU 5148 @ 2.33GHz Supermicro X7DB8 motherboard