From: Octavio Alvarez Piza <alvarezp@alvarezp.ods.org>
To: Hugh Dickins <hugh@veritas.com>
Cc: Dave Jones <davej@redhat.com>,
Arjan van de Ven <arjan@infradead.org>,
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: Wed, 11 Jan 2006 08:58:43 -0800 [thread overview]
Message-ID: <20060111085843.1d79e045@octavio.alvarezp.pri> (raw)
In-Reply-To: <Pine.LNX.4.61.0601111603520.4337@goblin.wat.veritas.com>
On Wed, 11 Jan 2006 16:12:54 +0000 (GMT)
Hugh Dickins <hugh@veritas.com> wrote:
> On Wed, 11 Jan 2006, Octavio Alvarez Piza wrote:
> > On Thu, 05 Jan 2006 11:00:41 -0800
> > "Octavio Alvarez" <alvarezp@alvarezp.ods.org> wrote:
> >
> > I have found another instance of "bad_page_state" with mapcount:-1
> > before hitting BUG_ON().
> >
> > Bad page state at free_hot_cold_page (in process 'X', page c1140c60)
> > flags:0x80010008 mapping:00000000 mapcount:-65536 count:0
>
> No, that's mapcount -65536 not -1.
>
That's right, this might be a different issue. Now that it was X and not
"kswap0d" and that Arjan has asked me, I've realized that I'm using the
binary nVidia driver. I had gotten pretty much the same issue with the
open driver, though. Still, since I changed kernels to 2.6.15, I'll try
again to catch the bad page state with the nv free driver.
> That means page->_mapcount contained 0xfffeffff when it should have
> contained 0xffffffff. A single bit got cleared. Probably bad memory,
> overheating, something of that kind.
BTW, what's the first 8 in flags:0x80010008? I can't find 1<<31 in
include/linux/page-flags.h
Octavio.
next prev parent reply other threads:[~2006-01-11 17:03 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
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 [this message]
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=20060111085843.1d79e045@octavio.alvarezp.pri \
--to=alvarezp@alvarezp.ods.org \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=davej@redhat.com \
--cc=hugh@veritas.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®