From: Olof Johansson <olof@lixom.net>
To: linux-ide@vger.kernel.org, jgarzik@pobox.com
Cc: linux-kernel@vger.kernel.org
Subject: [regression] 2.6.23 sata_mv EH updates broke my 7042 controller
Date: Mon, 1 Oct 2007 17:04:39 -0500 [thread overview]
Message-ID: <20071001220439.GA15332@lixom.net> (raw)
Hi,
I just pulled out my Marvell 7042 SATA controller here to give it a spin
and noticed that it no longer worked (i.e. init segvs when loading from
it), etc. 2.6.22 is fine.
Bisecting (just the file drivers/ata/sata_mv.c) resulted in
bdd4dddee325a7dce3e84cf48201a06aa8508aa4 popping out as the culprit
(file version 4537deb5e90b717a725b3d74b58b4bb1d28443d0 is fine).
Just for sanity checking: Has anyone else used 7042/6042 with the current
mainline driver?
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.
-Olof
next reply other threads:[~2007-10-01 22:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-01 22:04 Olof Johansson [this message]
2007-10-01 22:37 ` [regression] 2.6.23 sata_mv EH updates broke my 7042 controller Jeff Garzik
2007-10-02 2:30 ` Olof Johansson
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=20071001220439.GA15332@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).