All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Andrew Morton <akpm@osdl.org>,
	nickpiggin@yahoo.com.au, linux-kernel@vger.kernel.org
Subject: Re: mm/rmap.c negative page map count BUG.
Date: Thu, 5 Jan 2006 06:26:11 -0500	[thread overview]
Message-ID: <20060105112611.GM20809@redhat.com> (raw)
In-Reply-To: <1136459923.2920.17.camel@laptopd505.fenrus.org>

On Thu, Jan 05, 2006 at 12:18:43PM +0100, Arjan van de Ven wrote:
 > On Thu, 2006-01-05 at 06:15 -0500, Dave Jones wrote:
 > > On Thu, Jan 05, 2006 at 09:11:51AM +0100, Arjan van de Ven wrote:
 > >  > 
 > >  > > Quite a few Fedora users have hit it over the last year,
 > >  > > but what I find fascinating is that there's not a single
 > >  > > occurance of "BUG at mm/rmap.c" in our 2.6.9 based RHEL4 bug reports.
 > >  > 
 > >  > could mean it's caused by consumer hardware code...
 > > 
 > > Yeah. People buying enterprise distros do tend to buy branded RAM
 > > with goodies like ECC from big name suppliers instead of a cheap $20
 > > noname DIMM from "Joe's computers".
 > > 
 > > So it *could* be a lot of these are crappy hardware, especially
 > > as some of the reports do indicate that the problem went away
 > > when they upgraded their RAM.  Some of the others though, I'm
 > > not so sure.
 > 
 > it could also be some consumer-mostly device, or driver thereof. say
 > video capture or weird usb gizmo

except looking at the oopses, there's no obvious pattern amongst
the modules loaded.  Though they could all have a commonality as
a built-in driver, it's a long-shot.

even looking at the Fedora ones alone, which have no built-in
drivers, there's nothing that immediately jumps out like
"ooh, radeon again".  I'll look through them again tomorrow,
but first, sleep.

		Dave


  reply	other threads:[~2006-01-05 11:26 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-03  8:26 mm/rmap.c negative page map count BUG Dave Jones
2006-01-03 11:42 ` Nick Piggin
2006-01-03 13:53   ` Dave Jones
2006-01-04 23:53     ` Andrew Morton
2006-01-04 23:56       ` Dave Jones
2006-01-05  0:16         ` Andrew Morton
2006-01-05  0:31           ` Dave Jones
2006-01-05  7:47       ` Dave Jones
2006-01-05  8:11         ` Arjan van de Ven
2006-01-05 11:15           ` Dave Jones
2006-01-05 11:18             ` Arjan van de Ven
2006-01-05 11:26               ` Dave Jones [this message]
2006-01-05 19:00             ` Octavio Alvarez
2006-01-11  8:01               ` Octavio Alvarez Piza
2006-01-11 16:12                 ` Hugh Dickins
2006-01-11 16:21                   ` Arjan van de Ven
2006-01-11 16:58                   ` Octavio Alvarez Piza
2006-01-11 17:18                     ` Hugh Dickins
2006-01-11 17:24                     ` Andrew Morton

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=20060105112611.GM20809@redhat.com \
    --to=davej@redhat.com \
    --cc=akpm@osdl.org \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    /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.