From: Sean MacLennan <smaclennan@pikatech.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: BUG: Bad page map in process
Date: Fri, 4 Dec 2009 11:37:13 -0500 [thread overview]
Message-ID: <20091204113713.5b5e64a0@opus.seanm.ca> (raw)
In-Reply-To: <1259925535.2076.1275.camel@pasglop>
On Fri, 04 Dec 2009 22:18:55 +1100
Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
> 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 ?
It hasn't happened that often, but I have been focusing on 2.6.31.
So far, it has always happened well after the boot, but not hours. I
haven't worked out a specific workload.
Cheers,
Sean
next prev parent reply other threads:[~2009-12-04 16:37 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
2009-12-04 16:37 ` Sean MacLennan [this message]
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=20091204113713.5b5e64a0@opus.seanm.ca \
--to=smaclennan@pikatech.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.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).