From: Hugh Dickins <hugh@veritas.com>
To: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: Kernel BUG at mm/rmap.c:491
Date: Thu, 24 Nov 2005 08:04:39 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.61.0511240754190.5688@goblin.wat.veritas.com> (raw)
In-Reply-To: <200511232256.jANMuGg20547@unix-os.sc.intel.com>
On Wed, 23 Nov 2005, Chen, Kenneth W wrote:
> Has people seen this BUG_ON before? On 2.6.15-rc2, x86-64.
>
> Bad page state at free_hot_cold_page (in process 'sh', page ffff81000482dde8)
> flags:0x8000000000000000 mapping:0000000000000000 mapcount:1 count:0
> Bad page state at free_hot_cold_page (in process 'sh', page ffff8100049d0f78)
> flags:0x8000000000000000 mapping:0000000000000000 mapcount:1 count:0
> Bad page state at free_hot_cold_page (in process 'sh', page ffff8100049d0f40)
> flags:0x8000000000000004 mapping:0000000000000000 mapcount:1 count:0
> Kernel BUG at mm/swap.c:218
> Kernel BUG at mm/rmap.c:491
Neither mm/rmap.c (page_remove_rmap) nor mm/swap.c (put_page_testzero)
BUG is interesting in this case, they're just side-effects of trying to
recover from the preceding "Bad page state"s.
Which are interesting. Not at all the same case as the many recently
reported while we were fixing up PageReserved removal cases; though
yours will probably be related.
It could conceivably be an effect of a DRM pci_alloc_consistent issue
which Dave Airlie spotted yesterday; but not a typical case of it,
and I'm probably only thinking of that one because it's uppermost.
Please send your .config (I hope it's tailored somewhat to your machine,
rather than an allyesconfig or the like?) and bootup dmesg, in case they
help to narrow the search. You were just running straight 2.6.15-rc2,
no additional patches? Doing anything interesting just before this
happened?
Thanks,
Hugh
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2005-11-24 8:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-23 22:56 Chen, Kenneth W
2005-11-23 23:24 ` Con Kolivas
2005-11-23 23:33 ` Chen, Kenneth W
2005-11-23 23:35 ` Con Kolivas
2005-11-23 23:38 ` Alistair John Strachan
2005-11-23 23:40 ` Con Kolivas
2005-11-24 4:38 ` Dave Jones
2005-11-23 23:36 ` Randy.Dunlap
2005-11-23 23:39 ` Randy.Dunlap
2005-11-23 23:35 ` Alistair John Strachan
2005-11-24 4:40 ` Dave Jones
2005-11-24 5:34 ` Lee Revell
2005-11-24 18:08 ` Zwane Mwaikambo
2005-11-24 6:57 ` Alistair John Strachan
2005-11-24 7:50 ` Hugh Dickins
2005-11-24 11:33 ` Lee Revell
2005-11-24 18:59 ` Dave Jones
2005-11-24 23:47 ` Keith Owens
2005-11-24 23:50 ` Con Kolivas
2005-11-25 10:43 ` Hugh Dickins
2005-11-25 10:45 ` Con Kolivas
2005-11-24 8:04 ` Hugh Dickins [this message]
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.61.0511240754190.5688@goblin.wat.veritas.com \
--to=hugh@veritas.com \
--cc=kenneth.w.chen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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