From: Ken MacFerrin <lists@macferrin.com>
To: Alistair John Strachan <s0348365@sms.ed.ac.uk>
Cc: Dave Spring <dspring@acm.org>,
linux-kernel@vger.kernel.org, Hugh Dickins <hugh@veritas.com>
Subject: Re: PROBLEM: kernel BUG at mm/rmap.c:486 - kernel 2.6.15-r1
Date: Fri, 10 Feb 2006 19:15:09 -0700 [thread overview]
Message-ID: <43ED48AD.6060106@macferrin.com> (raw)
In-Reply-To: <200602100013.15276.s0348365@sms.ed.ac.uk>
Alistair John Strachan wrote:
> On Thursday 09 February 2006 23:55, Dave Spring wrote:
>
>>Just for closure's sake:
>> This turned out to be a hardware problem.
>>Memtest86+ http://www.memtest.org/ found an intermittent and
>>pattern-sensitive memory error,
>>and only appearing at one or two random locations within the 256M module.
>>Replacing the dodgy RAM module did the trick.
>
>
> Thanks Dave. Any update on your problem Ken? I'm keen to hear whether you had
> crashes without the NVIDIA driver loaded.
>
Sorry, I got called out of town last weekend so I didn't get a chance to
try this out yet..
-Ken
next prev parent reply other threads:[~2006-02-11 2:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-01 18:22 PROBLEM: kernel BUG at mm/rmap.c:486 - kernel 2.6.15-r1 Dave Spring
2006-02-09 23:55 ` Dave Spring
2006-02-10 0:13 ` Alistair John Strachan
2006-02-11 2:15 ` Ken MacFerrin [this message]
2006-03-13 18:59 ` Ken MacFerrin
2006-03-14 19:04 ` Ken MacFerrin
-- strict thread matches above, loose matches on Subject: below --
2006-01-28 3:20 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
2006-03-12 12:41 ` Nick Piggin
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=43ED48AD.6060106@macferrin.com \
--to=lists@macferrin.com \
--cc=dspring@acm.org \
--cc=hugh@veritas.com \
--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.