From: vda <vda@port.imtp.ilyichevsk.odessa.ua>
To: linux-kernel@vger.kernel.org
Subject: OOM killer in 2.4.15pre1 still not 100% ok
Date: Thu, 22 Nov 2001 17:22:47 -0200 [thread overview]
Message-ID: <01112217224700.01298@manta> (raw)
Today I saw OOM killer in action for the very fist time.
Just want to inform that it still not 100% ok (IMHO):
I reconfigured my text box for NFS root fs operation
and turned off swap. The box has 128M RAM.
At the time of OOM I was in Midnight Commander on normal vc (not xterm).
X+KDE (Kmail and a couple of Konquerors) was loaded but I didn't work
in X a that moment.
OOM killed top. I have top permanently running on vc10.
I presume it was neither big nor newly fired process so I don't think it was
right candidate for kill.
Last top screen is below.
(How nice: OOM killer taking snapshots of processes at kill time,
i.e. aids in its own debugging! :-)
(Oh, nice idea: dump top-like info in syslog after each OOM kill?)
--
vda
5:01pm up 1:08, 3 users, load average: 0.18, 0.10, 0.06
61 processes: 58 sleeping, 2 running, 1 zombie, 0 stopped
CPU states: 1.9% user, 15.6% system, 0.0% nice, 82.3% idle
Mem: 126272K av, 123428K used, 2844K free, 0K shrd, 16K buff
Swap: 0K av, 0K used, 0K free 47748K cached
PID USER PRI NI SIZE RSS SHARE STAT LIB %CPU %MEM TIME COMMAND
4 root 15 0 0 0 0 SW 0 13.8 0.0 0:02 kswapd
974 root 9 0 4852 4852 4724 S 0 2.3 3.8 0:17 mpg123
693 user0 9 0 1440 1440 1232 R 0 0.3 1.1 0:19 top c s
790 root 9 0 5052 5052 4756 S 0 0.1 4.0 0:08 kdeinit: kded
816 root 9 0 9428 9428 8080 S 0 0.1 7.4 0:01 kdeinit:
kdesktop
975 root 9 0 1708 1708 1592 S 0 0.1 1.3 0:00 mpg123
1 root 8 0 188 188 160 S 0 0.0 0.1 0:05 init
2 root 9 0 0 0 0 SW 0 0.0 0.0 0:00 keventd
3 root 19 19 0 0 0 SWN 0 0.0 0.0 0:00
ksoftirqd_CPU0
5 root 9 0 0 0 0 SW 0 0.0 0.0 0:00 bdflush
6 root 9 0 0 0 0 SW 0 0.0 0.0 0:00 kupdated
7 root 9 0 0 0 0 SW 0 0.0 0.0 0:00 eth0
8 root 9 0 0 0 0 SW 0 0.0 0.0 0:00 rpciod
14 root 9 0 580 580 496 S 0 0.0 0.4 0:00 devfsd /dev
687 root 9 0 624 624 528 S 0 0.0 0.4 0:00 syslogd
690 root 9 0 1120 1120 444 S 0 0.0 0.8 0:00 klogd -c 3
702 root 9 0 124 124 96 S 0 0.0 0.0 0:00 dhcpcd -t 20
-R -d eth1
734 rpc 9 0 644 644 540 S 0 0.0 0.5 0:00 rpc.portmap
736 root 9 0 556 556 484 S 0 0.0 0.4 0:00 inetd
738 root 9 0 664 664 564 S 0 0.0 0.5 0:00 automount
--timeout 5 /mnt/auto
740 root 9 0 488 488 420 S 0 0.0 0.3 0:00 gpm -2 -m
/dev/psaux -t ps2
741 root 9 0 484 484 424 S 0 0.0 0.3 0:00 /sbin/agetty
38400 tty1 linux
743 root 9 0 1168 1168 892 S 0 0.0 0.9 0:00 -bash
745 root 9 0 1168 1168 892 S 0 0.0 0.9 0:00 -bash
748 root 9 0 484 484 424 S 0 0.0 0.3 0:00 /sbin/agetty
38400 tty4 linux
749 root 9 0 484 484 424 S 0 0.0 0.3 0:00 /sbin/agetty
38400 tty5 linux
752 root 9 0 484 484 424 S 0 0.0 0.3 0:00 /sbin/agetty
38400 tty6 linux
753 root 9 0 484 484 424 S 0 0.0 0.3 0:00 /sbin/agetty
38400 tty7 linux
754 root 9 0 1116 1116 820 S 0 0.0 0.8 0:00 nmbd
-l/var/log/samba/nmbd.log -
755 root 9 0 1168 1168 1060 S 0 0.0 0.9 0:00 -bash
next reply other threads:[~2001-11-22 15:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-22 19:22 vda [this message]
2001-11-22 16:15 ` OOM killer in 2.4.15pre1 still not 100% ok Ryan Cumming
2001-11-22 21:42 ` vda
2001-11-23 15:00 ` vda
2001-11-26 10:24 ` Helge Hafting
2001-11-22 20:10 ` Mike Galbraith
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=01112217224700.01298@manta \
--to=vda@port.imtp.ilyichevsk.odessa.ua \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox