From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Aaro Koskinen <aaro.koskinen@iki.fi>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: kernel BUG at arch/powerpc/mm/hash_utils_64.c:1223!
Date: Fri, 08 Feb 2013 13:34:18 +1100 [thread overview]
Message-ID: <1360290858.2650.50.camel@pasglop> (raw)
In-Reply-To: <20130207230900.GC3178@blackmetal.musicnaut.iki.fi>
On Fri, 2013-02-08 at 01:09 +0200, Aaro Koskinen wrote:
>
> I get this BUG when enabling DEBUG_PAGEALLOC with 3.8-rc6+
> (6bacaa9ddacb71c691d32c678d37bc59ffc71fac) on G5 PPC.
>
> It seems to be fairly reproducible - I saw it 3 times, soon after
> booting
> while running a compilation job on ext3 partition. Unfortunately I'm
> not able to capture the full trace at the moment. Kernel config is
> below.
Thanks, I'll investigate.
Cheers,
Ben.
prev parent reply other threads:[~2013-02-08 2:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-07 23:09 kernel BUG at arch/powerpc/mm/hash_utils_64.c:1223! Aaro Koskinen
2013-02-08 2:34 ` Benjamin Herrenschmidt [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=1360290858.2650.50.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=aaro.koskinen@iki.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.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).