© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
I have had the same problem. Here is data from atop and syslog where oom killer runs:
-------
Here is my atop entry just before the oom killer hoses me:
-------
ATOP - velo 2008/12/16 10:29:32 600 seconds elapsed
PRC | sys 12m55s | user 2m31s | #proc 206 | #zombie 2 | #exit 300 |
CPU | sys 118% | user 27% | irq 1% | idle 205% | wait 49% |
cpu | sys 39% | user 17% | irq 1% | idle 27% | cpu000 w 16% |
cpu | sys 27% | user 5% | irq 0% | idle 58% | cpu003 w 11% |
cpu | sys 27% | user 3% | irq 0% | idle 58% | cpu001 w 12% |
cpu | sys 27% | user 2% | irq 0% | idle 61% | cpu002 w 10% |
CPL | avg1 17.48 | avg5 9.00 | avg15 4.28 | csw 1949602 | intr 709492 |
MEM | tot 4.0G | free 25.4M | cache 2.2G | buff 0.4M | slab 54.6M |
SWP | tot 0.0M | free 0.0M | | vmcom 3.4G | vmlim 7.9G |
PAG | scan 2368e5 | stall 0 | | swin 0 | swout 0 |
DSK | sda | busy 33% | read 38664 | write 11725 | avio 4 ms |
DSK | sdd | busy 2% | read 1625 | write 3420 | avio 2 ms |
DSK | sdb | busy 0% | read 125 | write 2 | avio 7 ms |
DSK | sdc | busy 0% | read 2 | write 2 | avio 5 ms |
NET | transport | tcpi 103286 | tcpo 101960 | udpi 463 | udpo 534 |
NET | network | ipi 103800 | ipo 102577 | ipfrw 0 | deliv 103800 |
NET | eth0 0% | pcki 16157 | pcko 28041 | si 222 Kbps | so 54 Kbps |
NET | lo ---- | pcki 74574 | pcko 74574 | si 344 Kbps | so 344 Kbps |
PID MINFLT MAJFLT VSTEXT VSIZE RSIZE VGROW RGROW MEM CMD 1/11
12668 222539 1202 103K 859.5M 659.6M 665.9M 549.1M 16% ld-linux.so.2
31287 333 283 24K 511.4M 319.8M 0K -27.1M 8% firefox
7402 80267 241 1592K 365.7M 175.9M 18256K -8800K 4% Xorg
-------
Here is the syslog entry where oom killer runs:
-------
Dec 16 10:31:17 velo kernel: [611084.971774] kded invoked oom-killer: gfp_mask=0x1201d2, order=0, oomkilladj=0
Notice that ld-linux.so.2 is the big memory user. Now, where is the problem?