similar to: dom0 nouvueau on 2.6.37 invokes OOM killer

Hey Jeremy, Please pull from devel/pat (based off your xen/dom0/core tree) which has one patch: Konrad Rzeszutek Wilk (1): xen/pat: make pte_flags(x) a pvops function. which is neccessary for the drivers/gpu/drm/radeon driver to work properly with AGP based cards (which look to be the only ones that try to set WC on pages). Also please pull from devel/kms.fixes-05 (based off your

Dynamically resizing the framebuffer on nv04 was like playing Russian roulette (and it often happened gratuitously) because it seems unable to scan out from buffers above 16MB. This patch splits the mappable VRAM into two chunks when that's the case, and makes the higher one to be used as well when applicable. Signed-off-by: Francisco Jerez <currojerez at riseup.net> ---

Added linux-btrfs and Helmut Hullen, who seemed to experience hangs on a T23 with BTRFS as well, to Cc. Am Thursday 03 February 2011 schrieb Rafael J. Wysocki: > This message has been generated automatically as a part of a report > of regressions introduced between 2.6.36 and 2.6.37. > > The following bug entry is on the current list of known regressions > introduced between

CENTOS-6.5 I had a kvm guest shutdown by oom-killer this morning. I have the syslog entries that pertain to this but they tell me little beyond that it happened. What must I look at to determine the root cause of this issue? How is it prevented? -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB at Harte-Lyne.ca Harte & Lyne Limited

Hi, It looks like what is happening is the Samba RPC server is forking a separate process for each NETLOGON connection it accepts. Normally, when the connection is closed, the child process will be cleaned up. On your setup, the connections appear to be left open (presumably due to the constant mail SSO queries), and so the rpc_server processes just accumulate. You had 669 rpc_server processes,

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

Hai, How is the swappiness set? cat /proc/sys/vm/swappiness Its probely set to 60, i suggest, lower it to 10 or 20. That wil help keeping the samba processes out of swap. I've see more programs gettting OOM Killed due too out of swap. echo 10 > /proc/sys/vm/swappiness Stop and start samba Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba

Hi Laurent, > > We upgraded a legacy (NT4) domain from 3.6 series to 4.8 and then 4.9.4 > samba version (using sernet subscription packages / debian stable) > > The setup is composed of 4 DCs with each 2 CPU/16GB RAM. > > We currently have ~700 user accounts / ~600 computers / ~150 groups > > Our mail setup, SSO, ... query the 4 DCs constantly. > > > Every 5 to

Hi Everyone I have sorted out the initial issues I''ve had and decided to give Xen another go. I''m trying to run Xen using kernel 2.6.37-rc3 (previous attempt with rc1 failed, and when I gave it a second go, rc3 was already out). As previously, 2.6.37-rc3 boots fine natively. 2.6.32 boots natively and under Xen as dom0, but I have reservations against running 2.6.32,

Hi Everyone I have sorted out the initial issues I''ve had and decided to give Xen another go. I''m trying to run Xen using kernel 2.6.37-rc3 (previous attempt with rc1 failed, and when I gave it a second go, rc3 was already out). As previously, 2.6.37-rc3 boots fine natively. 2.6.32 boots natively and under Xen as dom0, but I have reservations against running 2.6.32,

It looks like it was a quiet cycle for vhost-net: probably because most of energy was spent on bugfixes that went in for 2.6.36. People are working on multiqueue, tracing but I'm not sure it'll get done in time for 2.6.37 - so here's a tree with a single patch that helps windows guests which we definitely want in the next kernel. Please merge for 2.6.37. Thanks! The following changes

It looks like it was a quiet cycle for vhost-net: probably because most of energy was spent on bugfixes that went in for 2.6.36. People are working on multiqueue, tracing but I'm not sure it'll get done in time for 2.6.37 - so here's a tree with a single patch that helps windows guests which we definitely want in the next kernel. Please merge for 2.6.37. Thanks! The following changes

Just did some testing.. root at vicky:~# cat /var/log/auth.log | grep "Set" May 30 21:41:05 vicky sshd[1568]: Set /proc/self/oom_adj from -17 to -17 May 30 21:41:07 vicky sshd[1574]: Set /proc/self/oom_adj to -17 root at vicky:~# ps faux | grep 1574 root 1574 0.0 0.0 70488 3404 ? Ss 21:41 0:00 \_ sshd: root at pts/1 root at vicky:~# ps faux | grep

Hello All, Anyone have seen this before? Did samba_spnupdate really caused the crash??? [ 49.753564] block drbd1: drbd_sync_handshake: [ 49.753571] block drbd1: self BB16E125AF60AEDC:0000000000000000:30D97136FB1DA7A3:30D87136FB1DA7A3 bits:0 flags:0 [ 49.753576] block drbd1: peer 6365B5AFF049F16D:BB16E125AF60AEDD:30D97136FB1DA7A2:30D87136FB1DA7A3 bits:1 flags:0 [ 49.753580] block drbd1:

https://bugs.freedesktop.org/show_bug.cgi?id=34348 Summary: (regression/bisected) (2.6.37 nouveau/KMS) internal laptop display remains blank Product: xorg Version: unspecified Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component:

Here is a small btrfs vs. ext4 benchmark with kernel 2.6.37-rc1. compilebench with options -i 10 -r 30 on 2.6.37-rc1 btrfs ========================================================================== intial create total runs 10 avg 73.11 MB/s (user 0.34s sys 1.96s) create total runs 5 avg 49.53 MB/s (user 0.41s sys 1.62s) patch total runs 4 avg 22.13 MB/s (user 0.09s sys 1.79s) compile total runs

Hi, I''m working on the following topic from the xen roadmap as a part of an academic project: "Improve interaction between balloon driver and page allocator to avoid memory crunch." I have a few doubts regarding what exactly needs to be done: 1. Should the working of the balloon driver be same as in the case of VMware ESX balloon driver? (

I had the dom0 which unfortunately didn''t have a console on it hit a race condition and saw oom errors on it also. This happened after it was running for over 36 hours with a domU whose load average was avg was around 3 most of the time. changeset: 7396:9b51e7637676 Dom0 - UP i686, Centos 4.1, 768 megs domU-1 92 megs snmpd domU-2 92 megs snmpdd domU-3 410 megs postgres, tomcat 5.5,

When booting 2.6.37 (from kernel.org) under Xen 4.1, there are apparently issues with timer interrupts being delivered to the dom0. Repeatedly causing an interrupt (for example, the ACPI power button) will allow the system to boot, as does adding "clocksource=jiffies" to the kernel command line. This is only present under Xen, not when booting the same kernel on real hardware. When boot

Under both XEN 3.0.4 (2.6.16.33) and XEN 3.1 (2.6.18), I can make the OOM killer appear in dom0 of my server by doing heavy I/O from within a VM. If I start 5 VMs on the same server, each VM doing constant I/O over its boot disk (read/write a 2GB file), after about 30 minutes the OOM killer appears in dom0 and starts killing processes. This was observed using 256MB in dom0. If I bump the memory in