From: Hugh Dickins <hugh@veritas.com>
To: John Heil <kerndev@sc-software.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Bug: 2.6.24-smp: Eeek! page_mapcount(page) went negative! (-1)
Date: Wed, 6 Feb 2008 19:55:36 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.64.0802061948380.32204@blonde.site> (raw)
In-Reply-To: <Pine.LNX.4.64.0802061003370.4601@sc-software.com>
On Wed, 6 Feb 2008, kerndev@sc-software.com wrote:
>
> Before digging into this myself (don't really have enought time),
> I thought I'd submit it here...
Thanks for the report.
> Feb 6 09:09:47 sc-software kernel: Eeek! page_mapcount(page) went negative!
These very often turn out the be due to bad RAM or some such:
worth running memtest86+ overnight when you can, though its
success wouldn't be conclusive.
> (-1)
> Feb 6 09:09:47 sc-software kernel: page pfn = 12b1b1
> Feb 6 09:09:47 sc-software kernel: page->flags = 80080014
> Feb 6 09:09:47 sc-software kernel: page->count = 0
That's a free page which shouldn't have appeared in the pagetable.
It could be that there's a bit error somewhere in that pfn of 12b1b1.
> Feb 6 09:09:47 sc-software kernel: page->mapping = 00000000
> Feb 6 09:09:47 sc-software kernel: vma->vm_ops = 0x0
> Feb 6 09:09:47 sc-software kernel: ------------[ cut here ]------------
> Feb 6 09:09:47 sc-software kernel: kernel BUG at mm/rmap.c:631!
> Feb 6 09:09:47 sc-software kernel: invalid opcode: 0000 [#2] PREEMPT SMP
> Feb 6 09:09:47 sc-software kernel: Modules linked in: shpchp pci_hotplug
> ohci1394 ieee1394
> Feb 6 09:09:47 sc-software kernel:
> Feb 6 09:09:47 sc-software kernel: Pid: 3710, comm: X Tainted: G D
But that [#2] and that D taint both say there was already a problem
before this: anything showing in the log for that?
Hugh
next prev parent reply other threads:[~2008-02-06 19:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-06 18:13 kerndev
2008-02-06 19:55 ` Hugh Dickins [this message]
2008-02-06 20:21 ` kerndev
2008-02-06 20:33 ` Pekka Enberg
2008-02-06 20:38 ` kerndev
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=Pine.LNX.4.64.0802061948380.32204@blonde.site \
--to=hugh@veritas.com \
--cc=kerndev@sc-software.com \
--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
all inboxes | Powered by JetHome®