From: Alistair John Strachan <s0348365@sms.ed.ac.uk>
To: Ken MacFerrin <lists@macferrin.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: kernel BUG at mm/rmap.c:486 - kernel 2.6.15-r1
Date: Sat, 28 Jan 2006 19:13:50 +0000 [thread overview]
Message-ID: <200601281913.50169.s0348365@sms.ed.ac.uk> (raw)
In-Reply-To: <43DAE307.5010306@macferrin.com>
On Saturday 28 January 2006 03:20, Ken MacFerrin wrote:
> I started getting hard lockups on my desktop PC with the error "kernel
> BUG at mm/rmap.c:487" starting with kernel 2.6.13 and continuing through
> 2.6.14. After switching to 2.6.15 the lockups have continued with the
> message "kernel BUG at mm/rmap.c:486".
>
> The frequency and circumstance are completely random which originally
> had me suspecting bad memory but after running Memtest86+ for over 12
> hours without error I'm at a loss.
>
> I'm running the binary Nvidia driver so I'll understand if I can't get
> help here but in searching through the list archives it would seem I'm
> not alone and I am willing to try any patches that may help diagnose the
> issue. The crash happens at least daily and I've seen no difference in
> running kernels with or without PREEMPT enabled.
>
> The machine is a P4 3.00GHz with 2048MB PC3200 Unbuffered RAM on an ASUS
> motherboard with an ICH5 chipset. XFX GF 6600GT video card, 600W power
> supply and plenty of cooling.
Ken,
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.
--
Cheers,
Alistair.
'No sense being pessimistic, it probably wouldn't work anyway.'
Third year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.
next prev parent reply other threads:[~2006-01-28 19:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
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=200601281913.50169.s0348365@sms.ed.ac.uk \
--to=s0348365@sms.ed.ac.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@macferrin.com \
/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
all inboxes | Powered by JetHome®