From: Dave Spring <dspring@acm.org>
To: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: kernel BUG at mm/rmap.c:486 - kernel 2.6.15-r1
Date: Wed, 01 Feb 2006 18:22:13 +0000 [thread overview]
Message-ID: <43E0FC55.6080503@acm.org> (raw)
>> 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.
It's not the nv drivers - or at least not just them.
I'm getting this bug once or twice a day on a mini-ITX
(C3 533Mhz processor) based server which doesn't even have X installed.
For me, it appeared sometime after 2.6.12.
I'm now running with gentoo 2.6.15-r1 with Hugh's recently posted patch,
and waiting 8-|
Dave Spring
next reply other threads:[~2006-02-01 18:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-01 18:22 Dave Spring [this message]
2006-02-09 23:55 ` PROBLEM: kernel BUG at mm/rmap.c:486 - kernel 2.6.15-r1 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
-- 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=43E0FC55.6080503@acm.org \
--to=dspring@acm.org \
--cc=linux-kernel@vger.kernel.org \
/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