mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Octavio Alvarez" <alvarezp@alvarezp.ods.org>
To: "Dave Jones" <davej@redhat.com>,
	"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, 05 Jan 2006 11:00:41 -0800	[thread overview]
Message-ID: <op.s2w4pyqm4oyyg1@octavio.tecbc.mx> (raw)
In-Reply-To: <20060105111520.GL20809@redhat.com>

On Thu, 05 Jan 2006 03:15:20 -0800, Dave Jones <davej@redhat.com> 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.

Nevertheless, there are more instances of the bug in recent versions.
For me, version 2.6.10 or 2.6.11 seems to be the big difference, from
1 bug monthly to --suddenly-- 4 weekly.

I'm experiecing that problem too. I have notice that sometimes
"bad_page_state" trigger before the BUG is reported.

http://lkml.org/lkml/2005/12/14/449

I have already installed the instrumentation Dave provided. I'll see how
it goes.


  parent reply	other threads:[~2006-01-05 19:04 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-03  8:26 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
2006-01-05 19:00             ` Octavio Alvarez [this message]
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=op.s2w4pyqm4oyyg1@octavio.tecbc.mx \
    --to=alvarezp@alvarezp.ods.org \
    --cc=akpm@osdl.org \
    --cc=arjan@infradead.org \
    --cc=davej@redhat.com \
    --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 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®