linux-kernel - Re: OOM killer invoked on 2.6.24.4

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <e2e108260806141223l3545ea5ao2dc76325259bd3e8@mail.gmail.com>
Date:	Sat, 14 Jun 2008 21:23:23 +0200
From:	"Bart Van Assche" <bart.vanassche@...il.com>
To:	"Marco Barbero" <marco.barbero@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: OOM killer invoked on 2.6.24.4

On Sat, Jun 14, 2008 at 7:34 PM, Marco Barbero <marco.barbero@...il.com> wrote:
>> One or more processes on your system used too much memory. Dumping the
>> output of the following command periodically (e.g. every 10 minutes)
>> to a file will tell you which process is using too much memory:
>
>> { ps aux | head -n 1; ps aux | sort -n +4 | tail -n 10; }
>
> I'll do it.  Have to say that this box had an uptime of 1 month and
> never show issues. Also oom was invoked in the night when load is
> minimum.
> Could be related to slab and the quicklist leak?

Are you running the kernel in 32-bit mode ? Wouldn't it be better to
run a 64 bit kernel with 4 GB RAM ?

Bart.
--
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/