From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Jérôme Carretero" <cJ-ko@zougloub.eu>
Cc: Tejun Heo <tj@kernel.org>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
linux-ide@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Bad DMA from Marvell 9230
Date: Fri, 30 May 2014 20:37:58 +1000 [thread overview]
Message-ID: <1401446278.14938.26.camel@pasglop> (raw)
In-Reply-To: <20140530030618.5ad4f447@Vantage>
On Fri, 2014-05-30 at 03:06 -0400, Jérôme Carretero wrote:
> On Thu, 27 Mar 2014 17:57:37 +1100
> Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
>
> > I've been trying a 9230 on a power box here (a 9235 on the same
> > machine works fine) and it blows up with an IOMMU violation early
> > during init.
>
> Hi,
>
> That's https://bugzilla.kernel.org/show_bug.cgi?id=42679
> if you haven't already found it.
Somewhat... It's not the phantom function, the error I capture in my
IOMMU shows that it's trying to read from address 0 which is unmapped
but with the right initiator.
This device is a pile of crap. We've talked to Marvell support channel,
sent driver traces etc... but they didn't admit anything.
We've switched to a 9235 instead which seems to work fine.
Cheers,
Ben.
next prev parent reply other threads:[~2014-05-30 10:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 6:57 Bad DMA from Marvell 9230 Benjamin Herrenschmidt
2014-03-27 15:19 ` Tejun Heo
2014-04-05 2:35 ` Robert Hancock
2014-05-30 7:06 ` Jérôme Carretero
2014-05-30 10:37 ` Benjamin Herrenschmidt [this message]
2014-05-30 13:58 ` Jérôme Carretero
2014-05-30 14:13 ` Roger Heflin
2014-05-30 15:14 ` Jérôme Carretero
2014-05-30 21:06 ` Benjamin Herrenschmidt
2014-05-30 23:08 ` Roger Heflin
2014-05-30 20:59 ` 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=1401446278.14938.26.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=b.zolnierkie@samsung.com \
--cc=cJ-ko@zougloub.eu \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@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 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.