linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Gerhard Pircher <gerhard_pircher@gmx.net>
Cc: linuxppc-dev@ozlabs.org, Kumar Gala <kumar.gala@freescale.com>
Subject: Re: BUG() in current git, __dma_alloc_coherent, Beige G3
Date: Mon, 16 Jun 2008 17:11:27 +1000	[thread overview]
Message-ID: <1213600287.8129.125.camel@pasglop> (raw)
In-Reply-To: <20080616070359.300020@gmx.net>


> I discovered this bug some time ago and reported it on the list.
> See here for more info:
> http://ozlabs.org/pipermail/linuxppc-dev/2008-May/056128.html
> Anyway I don't think your machine needs dma-noncoherent.

Kumar, do you have a fix for that ?

Cheers,
Ben.

  reply	other threads:[~2008-06-16  7:11 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 [this message]
2008-06-16  7:30   ` Joseph Fannin
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=1213600287.8129.125.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=gerhard_pircher@gmx.net \
    --cc=kumar.gala@freescale.com \
    --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).