linux-kernel - Re: Oom-killer error.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 7 Nov 2007 08:45:34 +1100
From:	Nick Piggin <nickpiggin@...oo.com.au>
To:	jim@...lzero.info
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Oom-killer error.

On Tuesday 06 November 2007 19:34, Jim van Wel wrote:
> Hi there,
>
> I have a strange problem with like 10-15 servers right now.
> We have here all HP DL380-G5 servers with kernel 2.6.22.6. System all
> works normall. But after a uptime of like 15 a 25 days, we get these
> messages, and the servers is just crashed.
>

It is trying to allocate lowmem, but you have none left (and none
to speak of can be reclaimed).

I'd guess you have a kernel memory leak. Can you start by posting
the output of /proc/slabinfo and /proc/meminfo after the machine has
been up for 10-20 days (eg. close to OOM). And preferably also post
another set after just a day or so uptime.

Are you using the SLAB or SLUB allocator (check .config).

The kernel crashes (rather than recovers) because the leak has used
up all its working memory and killing processes does not release it.
(by the looks).

Thanks for the report,
Nick
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/