From: "Jim van Wel" <jim@coolzero.info>
To: "Michael Bussmann" <bus@mb-net.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: OOM killer on idle machine
Date: Tue, 5 Feb 2008 15:09:50 +0100 (CET) [thread overview]
Message-ID: <59776.81.171.100.191.1202220590.squirrel@webmail.coolzero.info> (raw)
In-Reply-To: <20080205140216.GD12009@ruf099.fkie.fgan.de>
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
>
next prev parent reply other threads:[~2008-02-05 14:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-05 10:04 OOM killer on idle machine Michael Bussmann
2008-02-05 11:08 ` Dhaval Giani
2008-02-05 11:41 ` Michael Bussmann
2008-02-06 8:30 ` Andrew Morton
[not found] ` <38602.81.171.100.191.1202213194.squirrel@webmail.coolzero.info>
[not found] ` <20080205140216.GD12009@ruf099.fkie.fgan.de>
2008-02-05 14:09 ` Jim van Wel [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-02-05 12:07 Jim van Wel
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=59776.81.171.100.191.1202220590.squirrel@webmail.coolzero.info \
--to=jim@coolzero.info \
--cc=bus@mb-net.net \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.