All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ken MacFerrin <lists@macferrin.com>
To: Jesper Juhl <jesper.juhl@gmail.com>,
	s0348365@sms.ed.ac.uk, hugh@veritas.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: kernel BUG at mm/rmap.c:486 - kernel 2.6.15-r1
Date: Sun, 29 Jan 2006 17:56:43 -0700	[thread overview]
Message-ID: <43DD644B.8070501@macferrin.com> (raw)
In-Reply-To: <43DD3DDF.6020901@macferrin.com>

Ken MacFerrin wrote:
> Jesper Juhl wrote:
> 
>> On 1/28/06, Ken MacFerrin <lists@macferrin.com> 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.
>>>
>>
>> If you don't actually *need* accelerated 3D (or if you could do
>> without it for a while), switching to the "nv" driver for a few
>> days/weeks would be interresting. If the crashes go away that would
>> point towards the nvidia driver, if they don't go away we'll get a
>> nice untainted crash report.
>>
> 
> Thanks to all for the response.  In hopes of helping to isolate this I 
> will move back over to the "nv" driver to see if I can recreate the 
> problem and get a clean bug report before applying Hugh's patch.
> 
> This crash currently happens daily for me so I should be able to test 
> this relatively quickly.
> -Ken

Unfortunately it seems that the "nv" driver in Xorg does not currently 
support multiple displays on a single video card with dual heads.  Not 
being able to at least run xinerama is a deal breaker for me so I'm back 
to the binary nvidia driver using twinview.  At this point I will apply 
Hugh's patch and post any further "Bad page state" and "Bad rmap"
messages as instructed.

Thanks,
Ken


  reply	other threads:[~2006-01-30  0:57 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 [this message]
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
  -- 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=43DD644B.8070501@macferrin.com \
    --to=lists@macferrin.com \
    --cc=hugh@veritas.com \
    --cc=jesper.juhl@gmail.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.