public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benoit Boissinot <bboissin@gmail.com>
To: Andrea Arcangeli <andrea@suse.de>
Cc: Hugh Dickins <hugh@veritas.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>, Mike Kirk <mike.kirk@sympatico.ca>
Subject: Re: 2.6.10-rc2-mm3 [was: Re: 2.6.9-rc2: "kernel BUG at mm/rmap.c:473!"]
Date: Wed, 1 Dec 2004 12:09:19 +0100	[thread overview]
Message-ID: <40f323d0041201030969c5dd92@mail.gmail.com> (raw)
In-Reply-To: <20041201011046.GY4365@dualathlon.random>

On Wed, 1 Dec 2004 02:10:46 +0100, Andrea Arcangeli <andrea@suse.de> wrote:
> On Wed, Dec 01, 2004 at 12:49:39AM +0000, Hugh Dickins wrote:
> > The atomic counter underflow in do_exit does suggest corruption
> > elsewhere than in transcode's page table (though I'm not at all
> > sure that is corrupt) - as always, it is worth giving memtest86
> > a thorough run to check your memory.
> 
> Transcode should be 99% cpu bound in userspace and it shouldn't be
> kernel intensive at all. It's one of the few desktop apps 99% cpu bound,
> in turn the reasoning that the cpu is overheating sounds reasonable to
> me. It might also be using sse2 to compress faster etc...
> 

I just did a memtest86 and it reported errors. It looks like my
hardware is faulty here.
Sorry for the inconvenience.

regards,

Benoit

      reply	other threads:[~2004-12-01 11:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-19  1:41 2.6.9-rc2: "kernel BUG at mm/rmap.c:473!" Mike Kirk
2004-09-19 12:07 ` Hugh Dickins
2004-11-30 15:06   ` 2.6.10-rc2-mm3 [was: Re: 2.6.9-rc2: "kernel BUG at mm/rmap.c:473!"] Benoit Boissinot
2004-12-01  0:49     ` Hugh Dickins
2004-12-01  1:10       ` Andrea Arcangeli
2004-12-01 11:09         ` Benoit Boissinot [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=40f323d0041201030969c5dd92@mail.gmail.com \
    --to=bboissin@gmail.com \
    --cc=akpm@osdl.org \
    --cc=andrea@suse.de \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mike.kirk@sympatico.ca \
    /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