All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Patrick Börjesson" <psycho@rift.ath.cx>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org,
	Alistair John Strachan <s0348365@sms.ed.ac.uk>
Subject: Re: PROBLEM: kernel BUG at mm/rmap.c:486 - kernel 2.6.15-r1
Date: Sun, 12 Mar 2006 14:12:07 +0100	[thread overview]
Message-ID: <20060312131207.GB17615@nexon> (raw)
In-Reply-To: <1142154323.2882.12.camel@laptopd505.fenrus.org>

[-- Attachment #1: Type: text/plain, Size: 1359 bytes --]

On 2006-03-12 10:05, Arjan van de Ven uttered these thoughts:
> On Sun, 2006-03-12 at 01:06 +0100, Patrick =?utf-8?Q?B=F6rjesson?=
> wrote:
> > > Just to let you know, I've had the same problem on x86-64. It's an
> > > incredibly rare fault here and I've not been able to reproduce it.
> > > However, I cannot help but notice that all of the reporters so far
> > > have been running the binary NVIDIA driver, including myself.
> > > 
> > > I would not be surprised if running without the NVIDIA driver
> > > eliminated the problem.
> > 
> > Not running either with the NVIDIA driver or with x86-64 on the machine
> > I'm getting this on, but I get it fairly often (as in: today I've
> > probably gotten it at least 5-10 times). It seems it's pretty bound by
> > either high CPU or disk usage, since I've always gotten it while
> > compiling stuff so far. Although my system doesn't hard lock if I get
> > this error; I can at least run most commands and ssh into it.
> 
> 
> just to rule the last issue out: this machine survives memtest86 ?

I'm sorry to have wasted your time; no, it didn't =\ 
Didn't think to run it before since the mem-stick in the machine is
pretty new (not more than 2 months). 

Sorry again,
Patrick Börjesson

-- 
/  ()  The ASCII Ribbon Campaign - against HTML Email
\  /\   and proprietary formats.

[-- Attachment #2: Type: application/pgp-signature, Size: 191 bytes --]

  reply	other threads:[~2006-03-12 13:12 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-28  3:20 PROBLEM: kernel BUG at mm/rmap.c:486 - kernel 2.6.15-r1 Ken MacFerrin
2006-01-28 15:48 ` Hugh Dickins
2006-02-02  1:17   ` Ken MacFerrin
2006-02-02 15:54     ` Hugh Dickins
2006-02-02 21:31       ` Ken MacFerrin
2006-01-28 18:31 ` Jesper Juhl
2006-01-29 22:12   ` Ken MacFerrin
2006-01-30  0:56     ` Ken MacFerrin
2006-01-30 16:46       ` Alistair John Strachan
2006-01-28 19:13 ` Alistair John Strachan
2006-03-12  0:06   ` Patrick B�rjesson
2006-03-12  2:06     ` Alistair John Strachan
2006-03-12  9:05     ` Arjan van de Ven
2006-03-12 13:12       ` Patrick Börjesson [this message]
2006-03-12 12:41     ` Nick Piggin
  -- strict thread matches above, loose matches on Subject: below --
2006-02-01 18:22 Dave Spring
2006-02-09 23:55 ` Dave Spring
2006-02-10  0:13   ` Alistair John Strachan
2006-02-11  2:15     ` Ken MacFerrin
2006-03-13 18:59       ` Ken MacFerrin
2006-03-14 19:04         ` Ken MacFerrin

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=20060312131207.GB17615@nexon \
    --to=psycho@rift.ath.cx \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=s0348365@sms.ed.ac.uk \
    /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.