From: Joseph Fannin <jfannin@gmail.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: BUG() in current git, __dma_alloc_coherent, Beige G3
Date: Mon, 16 Jun 2008 03:30:41 -0400 [thread overview]
Message-ID: <20080616073041.GA26917@nineveh.local> (raw)
In-Reply-To: <1213591838.8129.123.camel@pasglop>
On Mon, Jun 16, 2008 at 02:50:38PM +1000, Benjamin Herrenschmidt wrote:
> On Sun, 2008-06-15 at 21:46 -0400, Joseph Fannin wrote:
> > Hello!
> >
> > I'm reproducably hitting a BUG() in Linus' git (current as of about
> > noon, Sunday 15, GMT -0500) on my Beige PowerMac G3 (32bit, natch).
> > The line indicted in the (hand-copied) traceback that follows is:
> >
> > BUG_ON(!pte_none(*pte));
> >
> > ...in __dma_alloc_coherent().
>
> .../...
>
> > [ 261.043131] ------------[ cut here ]------------
> > [ 261.044194] kernel BUG at arch/powerpc/lib/dma-noncoherent.c:209!
>
> I wonder how you end up hitting code in dma-noncoherent.c in the first
> place ! PowerMac kernels should not have that code compiled in at all...
I think it's because PPC_PRPMC2800 and MPC5121_ADS both live under
PPC_MULTIPLATFORM, and end up selecting NOT_COHERENT_CACHE.
If the button in Kconfig isn't labeled "Do Not Push", heck, I'll build
it.
--
Joseph Fannin
jfannin@gmail.com
next prev parent reply other threads:[~2008-06-16 7:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-16 1:46 BUG() in current git, __dma_alloc_coherent, Beige G3 Joseph Fannin
2008-06-16 4:50 ` Benjamin Herrenschmidt
2008-06-16 7:03 ` Gerhard Pircher
2008-06-16 7:11 ` Benjamin Herrenschmidt
2008-06-16 7:30 ` Joseph Fannin [this message]
2008-06-16 9:05 ` Benjamin Herrenschmidt
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=20080616073041.GA26917@nineveh.local \
--to=jfannin@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.