public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Benoit Dejean <bdejean@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: mlock oops
Date: Mon, 25 Jul 2005 22:56:33 -0400	[thread overview]
Message-ID: <1122346593.1472.84.camel@mindpipe> (raw)
In-Reply-To: <aee4c5bc05072519431964a561@mail.gmail.com>

On Tue, 2005-07-26 at 04:43 +0200, Benoit Dejean wrote:
> Hi,
> 	i'm using Debian SID kernel-image-2.6.11-powerpc [1] (which is not
> tainted). I've unfortunately started sysutils [2] memtest as user (no caps, no
> sticky bit).
> 
> /usr/sbin/memtest all

> As expected, a few minutes later, my system was back. But an oops occured.

That's not an Oops...

> I was expecting the OOMK to rescue my system by killing memtest.
> 

This is exactly what happened:

> Out of Memory: Killed process 2386 (memtest).
> memtest: page allocation failure. order:0, mode:0xd2
> 

Lee


      reply	other threads:[~2005-07-26  2:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-26  2:43 mlock oops Benoit Dejean
2005-07-26  2:56 ` Lee Revell [this message]

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=1122346593.1472.84.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=bdejean@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox