From: Olof Johansson <olof@lixom.net>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [regression] 2.6.23 sata_mv EH updates broke my 7042 controller
Date: Mon, 1 Oct 2007 21:30:01 -0500 [thread overview]
Message-ID: <20071002023000.GA19286@lixom.net> (raw)
In-Reply-To: <470176B8.1000109@pobox.com>
On Mon, Oct 01, 2007 at 06:37:44PM -0400, Jeff Garzik wrote:
> Olof Johansson wrote:
>> Hardware config in my case:
>> Highpoint 2310 controller
>> PPC (big endian)
>> WD Raptor disk
>> Works fine with the other controller I've been using (SIL24), and works
>> fine if I revert the driver.
>> It also works fine if I disable the IOMMU. This would point towards
>> either a stale dma mapping, or a missing setup of one.
>> Not being much at home in the SATA drivers I could keep digging but I
>> figured I'd bring it up first in case it rings a bell for someone.
>
> The IOMMU data point is certainly interesting. Nothing jumps out on a
> re-review of the patch, so keep digging and let us know ;-)
Looks like it's caused by enabling vmerge (which tends to be on for the
common PPC defconfigs). If I disable it, things look OK.
Perhaps the Marvell controller doesn't like requests larger than 64K,
or wrapping some boundary. Do you have access to erratas/docs?
I have verified it on a powermac now as well (had a quick scare that it
might have been some problem with the PA Semi IOMMU, but no).
-Olof
next prev parent reply other threads:[~2007-10-02 2:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-01 22:04 [regression] 2.6.23 sata_mv EH updates broke my 7042 controller Olof Johansson
2007-10-01 22:37 ` Jeff Garzik
2007-10-02 2:30 ` Olof Johansson [this message]
2007-10-02 23:23 ` Jeff Garzik
2007-10-03 1:45 ` [PATCH] libata: fix for sata_mv >64KB DMA segments Olof Johansson
2007-10-03 18:43 ` Jeff Garzik
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=20071002023000.GA19286@lixom.net \
--to=olof@lixom.net \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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).