Re: OOM killer problem - how to read the kernel log?

["Tobias Brox" <tobixen@gmail.com>]

[Tobias Brox]
> > We're running 32 bits linux, maybe it would help to upgrade to 64 bits?

[Johannes Weiner]
> 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.

Point taken.  I've gotten quite some replies on this, also off the
list.  We will upgrade to 64 bits, but I don't know when we will get
that done, so now we're wondering what we can do for short-term
solutions.

[Tobias Brox]
> > 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.

[Hannes]
> kern.log has wrong permissions, slabinfo and meminfo are empty.

My oh my.  I'm really awfully bad at testing things.  Sorry for that.
Links should work now.  Ok, now it's even tested ;-)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/