From: Benjamin Herrenschmidt <benh@kernel•crashing.org>
To: Josh Boyer <jwboyer@gmail•com>
Cc: linuxppc-dev <linuxppc-dev@ozlabs•org>,
Sean MacLennan <smaclennan@pikatech•com>
Subject: Re: BUG: Bad page map in process
Date: Fri, 04 Dec 2009 22:18:55 +1100 [thread overview]
Message-ID: <1259925535.2076.1275.camel@pasglop> (raw)
In-Reply-To: <20091204110055.GP14279@hansolo.jdub.homelinux.org>
On Fri, 2009-12-04 at 06:00 -0500, Josh Boyer wrote:
> On Fri, Dec 04, 2009 at 08:08:27PM +1100, Benjamin Herrenschmidt wrote:
> >On Thu, 2009-12-03 at 14:18 -0500, Sean MacLennan wrote:
> >> With 2.6.32 I sometimes get lots and lots of "Bad page map" errors as
> >> shown below. I believe these started in 2.6.32-rc8 or possibly
> >> 2.6.32-rc7. Pika just switched to 2.6.31 so I have been concentrating
> >> on that release, and not really testing the 2.6.32 stream.
> >>
> >> I wish I could give more info, but I don't really even have the time to
> >> write this email :( I am hoping somebody will have a eureka moment.
> >
> >That's a concern. Remind me what CPU / MMU type is Pika using ?
>
> 440EP
Ok, I'll have a look next week. In the meantime, Sean, can you give me a
hint of what you do to trigger it ? Boot time ? specific workload ?
Cheers,
Ben.
next prev parent reply other threads:[~2009-12-04 11:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-03 19:18 BUG: Bad page map in process Sean MacLennan
2009-12-03 20:06 ` Jake Magee
2009-12-04 0:38 ` Sean MacLennan
2009-12-04 9:08 ` Benjamin Herrenschmidt
2009-12-04 11:00 ` Josh Boyer
2009-12-04 11:18 ` Benjamin Herrenschmidt [this message]
2009-12-04 16:37 ` Sean MacLennan
2009-12-08 0:56 ` Sean MacLennan
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=1259925535.2076.1275.camel@pasglop \
--to=benh@kernel$(echo .)crashing.org \
--cc=jwboyer@gmail$(echo .)com \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=smaclennan@pikatech$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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