From: Johannes Weiner <hannes-kernel@saeurebad.de>
To: Tobias Brox <tobixen@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: OOM killer problem - how to read the kernel log?
Date: Sat, 10 Nov 2007 15:02:12 +0100 [thread overview]
Message-ID: <20071110140212.GA20176@cataract> (raw)
In-Reply-To: <ef2af3100711091335y35c3d514u4faec75528fcec5b@mail.gmail.com>
Hi,
On Fri, Nov 09, 2007 at 10:35:14PM +0100, Tobias Brox wrote:
> We're running 32 bits linux, maybe it would help to upgrade to 64 bits?
Although you can address up to 64GB of RAM with PAE, the address space
of directly accessible memory is still at 32bit (4GB) and access to
higher memory costs low memory and processing overhead for the mapping
into the 32bit address space.
> I've copied out relevant files on
> http://oppetid.no/~tobixen/oom_problem/ - it's the complete kernel
> log, /proc/config.gz, /proc/slabinfo, /proc/meminfo and dmesg. Those
> are of course fetched after the reboot.
kern.log has wrong permissions, slabinfo and meminfo are empty.
Hannes
next prev parent reply other threads:[~2007-11-10 14:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-09 21:35 OOM killer problem - how to read the kernel log? Tobias Brox
2007-11-09 21:54 ` Douglas McNaught
2007-11-10 14:02 ` Johannes Weiner [this message]
2007-11-10 16:09 ` Tobias Brox
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=20071110140212.GA20176@cataract \
--to=hannes-kernel@saeurebad.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tobixen@gmail.com \
/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