Message-ID: <59776.81.171.100.191.1202220590.squirrel@webmail.coolzero.info>
In-Reply-To: <20080205140216.GD12009@ruf099.fkie.fgan.de>
References: <20080205100423.GA12009@ruf099.fkie.fgan.de>
    <38602.81.171.100.191.1202213194.squirrel@webmail.coolzero.info>
    <20080205140216.GD12009@ruf099.fkie.fgan.de>
Date: Tue, 5 Feb 2008 15:09:50 +0100 (CET)
Subject: Re: OOM killer on idle machine
From: "Jim van Wel" <jim@coolzero.info>
To: "Michael Bussmann" <bus@mb-net.net>
Cc: linux-kernel@vger.kernel.org
Reply-To: jim@coolzero.info
User-Agent: SquirrelMail/1.4.8-4.0.1.el4
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
Importance: Normal
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1096
Lines: 41

Funny,

I also got 32bits kernels running, and moving to 64bits because that's
more stable what we tested here...

Greetings,
Jim.

> Hi Jim,
>
> On 2008-02-05 13:06:34 +0100, Jim van Wel wrote:
>
>> http://lkml.org/lkml/2007/11/6/44
>
> Oops, I didn't expect the problem to be 3 months old.  Next time I'll
> browse the archives more thoroughly.
>
>> Got same issue, but somewhat different hardware. I'm really wondering,
>> are
>> you using a 64bits kernel or a 32bit?
>
> It's a 32-bit kernel.  Hmm, there are two similar systems at a customer's
> site with a 64-bit kernel that don't seem to be affected by this bug.
> Another system with a 32-bit kernel is still running, but it only has 2 GB
> RAM in it.  Interesting...
>
> Cheers,
> MB
>
> --
> Michael Bussmann <bus@mb-net.net>
> BOFH excuse #232:
>
> Ionization from the air-conditioning
>

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