From: Zwane Mwaikambo <zwane@arm.linux.org.uk>
To: Chris Wright <chrisw@osdl.org>
Cc: Andrew Morton <akpm@osdl.org>,
clameter@sgi.com, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Fixes for prep_zero_page
Date: Thu, 13 Jan 2005 17:50:41 -0700 (MST) [thread overview]
Message-ID: <Pine.LNX.4.61.0501131133230.4941@montezuma.fsmlabs.com> (raw)
In-Reply-To: <20050113102420.A469@build.pdx.osdl.net>
On Thu, 13 Jan 2005, Chris Wright wrote:
> * Zwane Mwaikambo (zwane@arm.linux.org.uk) wrote:
> > It looks like it's still not happy with CONFIG_DEBUG_PAGEALLOC under load.
> >
> > Unable to handle kernel paging request at virtual address ec5d97f4
>
> Is that in vmalloc space?
Hmm it looks like.
> > printing eip:
> > c014a882
> > *pde = 0083e067
> > Oops: 0000 [#1]
> > PREEMPT SMP DEBUG_PAGEALLOC
> > Modules linked in:
> > CPU: 0
> > EIP: 0060:[<c014a882>] Not tainted VLI
> > EFLAGS: 00010002 (2.6.10-mm2)
> > EIP is at check_slabuse+0x52/0xf0
>
> Hmm, isn't that from Manfred's patch to periodically scan? Doesn't look
> to me like it's related to the page prep fixup. What kind of load, etc?
I had an email exchange with Christopher and we came to the conclusion
that it's breakage elsewhere with CONFIG_DEBUG_PAGEALLOC.
prev parent reply other threads:[~2005-01-14 0:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-08 9:06 panic on bootup due to __GFP_ZERO patch Chris Wright
2005-01-08 20:00 ` Dave Jones
2005-01-09 9:45 ` Andrew Morton
2005-01-09 15:56 ` [PATCH] Fixes for prep_zero_page Zwane Mwaikambo
2005-01-09 20:52 ` Andrew Morton
2005-01-09 21:32 ` Zwane Mwaikambo
2005-01-09 22:48 ` Chris Wright
2005-01-10 4:18 ` Zwane Mwaikambo
2005-01-13 5:05 ` Zwane Mwaikambo
2005-01-13 18:24 ` Chris Wright
2005-01-14 0:50 ` Zwane Mwaikambo [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.0501131133230.4941@montezuma.fsmlabs.com \
--to=zwane@arm.linux.org.uk \
--cc=akpm@osdl.org \
--cc=chrisw@osdl.org \
--cc=clameter@sgi.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;
as well as URLs for NNTP newsgroup(s).