linux-kernel - Re: Help decoding oom-killer output

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, 08 Sep 2010 15:30:17 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Aaron Sowry <aaron@...dio.se>
Cc:	linux-kernel@...r.kernel.org, Pierre Ossman <ossman@...dio.se>
Subject: Re: Help decoding oom-killer output

Aaron Sowry <aaron@...dio.se> writes:

> After running in to problems with the amount of vmalloc memory on a SLED
> 11 SP1 system (due to a large number of ncp mounts), we have increased
> this with the kernel parameter 'vmalloc=512M'.

This means the 32bit kernel has only about 400MB low mem virtual
address space left, large parts of it being used by the mem_map
arrays. So whole kernel has to run in 100-200MB or so which
is likely not enough.

>
> Since this change, oom-killer seems to think we are running out of
> memory,

Yes you will run out of address space all the time for kernel
operations.

Real fix is to use 64bit instead. 32bit is so 90ies.

-Andi

-- 
ak@...ux.intel.com -- Speaking for myself only.
--
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/