From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Michael Harris <googlegroups@mgharris.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.18: Kernel BUG at mm/rmap.c:522
Date: Thu, 12 Oct 2006 18:16:18 +1000 [thread overview]
Message-ID: <452DF9D2.6020306@yahoo.com.au> (raw)
In-Reply-To: <20061011160740.GA6868@dingu.igconcepts.com>
Michael Harris wrote:
> Hi, I can readily reproduce this with 2.6.18 doing 4 simultanous kernel compiles on two disks to load test a P4 3.2 HT with 2GB. I have SMP and SMT scheduling enabled, and the 4GB memory option. Here is output with CONFIG_DEBUG_VM enabled followed by another crash before CONFIG_DEBUG_VM was enabled.
> Oct 11 04:53:35 hen kernel: swap_free: Unused swap offset entry 00004000
> Oct 11 04:53:35 hen kernel: Eeek! page_mapcount(page) went negative! (-1)
> Oct 11 04:53:35 hen kernel: page->flags = c0080014
> Oct 11 04:53:35 hen kernel: page->count = 0
> Oct 11 04:53:35 hen kernel: page->mapping = 00000000
Hmm, this is a new one. The page is free and not reserved, wheras we are
used to seeing them reserved here.
> Oct 11 04:54:31 hen kernel: Bad page state in process 'tripwire'
> Oct 11 04:54:31 hen kernel: page:c1b5cd80 flags:0xc0000014 mapping:00000000 mapcount:-1 count:0
> Another crash from a day earlier before enabling DEBUG_VM
> Oct 10 05:19:43 hen kernel: VM: killing process cc1
> Oct 10 05:19:43 hen kernel: swap_free: Unused swap offset entry 00002000
> Oct 10 05:19:56 hen kernel: swap_free: Unused swap offset entry 00000400
These unused swap offset entry messages seem to indicate extensive memory
corruption in your page tables. Probably bad RAM, or system overheating
when you load it up :(
Can you run a good memory tester like memtest86+ overnight?
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
next prev parent reply other threads:[~2006-10-12 8:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-11 16:07 2.6.18: Kernel BUG at mm/rmap.c:522 Michael Harris
2006-10-12 7:00 ` Andrew Morton
2006-10-12 7:28 ` Dave Jones
2006-10-12 8:16 ` Nick Piggin [this message]
2006-10-12 14:19 ` Michael Harris
2006-10-12 17:42 ` Nick Piggin
-- strict thread matches above, loose matches on Subject: below --
2006-10-04 10:40 Andre Noll
2006-10-04 13:59 ` Nick Piggin
2006-10-04 15:42 ` Andre Noll
2006-10-04 15:49 ` Peter Zijlstra
2006-10-04 16:12 ` Andre Noll
2006-10-04 20:39 ` Dave Jones
2006-10-05 6:28 ` 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=452DF9D2.6020306@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=googlegroups@mgharris.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