linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: list linux-ide <linux-ide@vger.kernel.org>
Subject: Re: DMA breakage in 2.6.29-rc*
Date: Fri, 30 Jan 2009 22:07:58 +1100	[thread overview]
Message-ID: <1233313678.18767.25.camel@pasglop> (raw)
In-Reply-To: <1233294371.18767.23.camel@pasglop>

On Fri, 2009-01-30 at 16:46 +1100, Benjamin Herrenschmidt wrote:
> Hi Bart !
> 
> On a bunch of pmac's, I'm getting lost interrupts when trying to do DMA
> with ide hard disks (first time at boot when reading the partition
> table). It then times out, reverts to PIO and boots fine.
> 
> Haven't had time to fully bisect yet, but it seem to be somewhere in the
> pile of IDE patches (surprise :-) that went in around that time.
> 
> I'll dig more next week, but in the meantime, I though you may have a
> possible candidate in mind.

Smells like the patch that popped up not long ago already (can't find
the thread now) where you cleaned up the port registration and broke our
trick of passing a different parent device than the one used for DMA or
something like that ... that mixed with something not testing the dma
map results (probably my fault) and I think we are passing crap DMA
addresses to the device.

I'll sort it out. I should be able to just add working dma ops to the
macio_device, it's a lot easier now that ppc32 has the same dma ops
structure in struct device as ppc64.

Cheers,
Ben.



  reply	other threads:[~2009-01-30 11:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-30  5:46 DMA breakage in 2.6.29-rc* Benjamin Herrenschmidt
2009-01-30 11:07 ` Benjamin Herrenschmidt [this message]
2009-02-01 16:44   ` Bartlomiej Zolnierkiewicz
2009-02-01 22:49     ` Benjamin Herrenschmidt
2009-02-01 23:07       ` Benjamin Herrenschmidt
2009-01-30 12:17 ` Mikael Pettersson
2009-01-30 20:45   ` 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=1233313678.18767.25.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=bzolnier@gmail.com \
    --cc=linux-ide@vger.kernel.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).