Messages in this thread | | | Date | Sat, 10 Nov 2007 15:02:12 +0100 | From | Johannes Weiner <> | Subject | Re: OOM killer problem - how to read the kernel log? |
| |
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 - 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/
| |