From: Andrew Morton <akpm@osdl.org>
To: Anton Titov <a.titov@host.bg>
Cc: linux-kernel@vger.kernel.org
Subject: Re: OOM Killer killing whole system
Date: Fri, 20 Jan 2006 04:11:14 -0800 [thread overview]
Message-ID: <20060120041114.7f06ecd8.akpm@osdl.org> (raw)
In-Reply-To: <1137337516.11767.50.camel@localhost>
Anton Titov <a.titov@host.bg> wrote:
>
> Yesterday I accidently noticed few OOM killer messages in the system log
> and leaved a console tailing the log for the night. In 6 in the morning
> OOM killer got mad generating 500 lines in the log and 5 minutes later
> system closed the ssh connection and became inresponsive. The guy in the
> datacenter told me that when he attached keyboard even caps lock was not
> working. Inspite of this the system still was responsive (only to) ping.
>
> The strange thing is this machine is relatively light loaded - now after
> 6 hours being up free shows:
> total used free shared buffers cached
> Mem: 2075468 1148564 926904 0 123472 314516
> -/+ buffers/cache: 710576 1364892
> Swap: 1004020 0 1004020
>
> Load average stays under 0.5 most of the time. In 6 in the morning it
> should be almost no load (there is no crons scheduled at that time).
>
> I'm attaching messages from the log and my .config.
What kernel version? <looks in config.gz>. 2.6.15.
> Jan 15 06:05:09 vip Normal free:3700kB min:3756kB low:4692kB high:5632kB active:9964kB inactive:8532kB present:901120kB pages_scanned:19628
Pretty much all of the ZONE_NORMAL memory is AWOL.
> Jan 15 06:05:09 vip 216477 pages slab
It's all in slab. 800MB.
I'd be suspecting a slab memory leak. If it happens again, please take a
copy of /proc/slabinfo, send it.
next prev parent reply other threads:[~2006-01-20 12:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-15 15:05 OOM Killer killing whole system Anton Titov
2006-01-20 12:11 ` Andrew Morton [this message]
2006-01-20 20:04 ` Chase Venters
2006-01-20 21:48 ` Anton Titov
2006-01-20 22:50 ` Andrew Morton
2006-01-21 0:09 ` Anton Titov
2006-01-21 0:19 ` Chase Venters
2006-01-21 0:50 ` Andrew Morton
2006-01-21 1:17 ` James Bottomley
2006-01-21 3:29 ` Anton Titov
2006-01-21 3:44 ` Andrew Morton
2006-01-25 22:20 ` Matthias Urlichs
2006-01-21 3:45 ` Anton Titov
2006-01-21 3:53 ` Chase Venters
2006-01-21 4:21 ` Anton Titov
2006-01-21 4:35 ` Chase Venters
2006-01-23 2:56 ` Kalin KOZHUHAROV
2006-01-23 3:28 ` Chase Venters
2006-01-23 8:39 ` Jens Axboe
2006-01-23 8:41 ` Arjan van de Ven
2006-01-23 9:10 ` Chase Venters
-- strict thread matches above, loose matches on Subject: below --
2006-01-23 12:55 Nicolas Mailhot
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=20060120041114.7f06ecd8.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=a.titov@host.bg \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.