From: Robert Hancock <hancockrwd@gmail.com>
To: Davidovac Zoran <davidovacz@gmail.com>
Cc: Jeff Garzik <jgarzik@pobox.com>, Tejun Heo <tj@kernel.org>,
linux-ide@vger.kernel.org
Subject: Re: kernel 3.6+ problem with Marvell 88SE9172 SATA Controller
Date: Sat, 05 Oct 2013 19:00:30 -0600 [thread overview]
Message-ID: <5250B62E.4080407@gmail.com> (raw)
In-Reply-To: <524E4C29.10506@gmail.com>
On 10/03/2013 11:03 PM, Davidovac Zoran wrote:
> Dear All,
>
> After I've upgraded from kernel 3.4.X to 3.10.14 and I noticed 2 drives
> missing that
> are connected on Marvell 88SE9172 SATA Controller.
>
> The last version that worked properly was 3.5.7, but any kernel above
> 3.6.0+ drives connected to Marvell are missing.
>
> This was tested on Board GA-X79-UD5
> http://www.gigabyte.com/products/product-page.aspx?pid=4049#sp
> that have 3 x Marvell 88SE9172 chips.
>
> tested kernels:
> linux-3.10.1.tar.xz linux-3.12-rc3.tar.xz linux-3.6.11.tar.xz
> linux-3.7.10.tar.xz
> linux-3.10.14.tar.xz linux-3.4.64.tar.xz linux-3.6.5.tar.xz
> linux-3.8.13.tar.xz
> linux-3.11.3.tar.xz linux-3.5.7.tar.xz linux-3.6.tar.xz
> linux-3.9.11.tar.xz
>
> 3.6.0+ dmesg:
> ata7.00: failed to IDENTIFY (INIT_DEV_PARAMS failed, err_mask=0x80)
> dmar: DRHD: handling fault status reg 502
> dmar: DMAR:[DMA Write] Request device [05:00.1] fault addr fffc0000
> DMAR:[fault reason 02] Present bit in context entry is clear
This is likely a known problem with some Marvell SATA controllers in
combination with the Intel IOMMU being enabled. The controller is
issuing DMA requests from the wrong device address which get blocked by
the IOMMU because that device isn't supposed to be accessing the memory.
I thought there was some efforts to add a workaround for this, but
haven't heard anything about it recently.
prev parent reply other threads:[~2013-10-06 1:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-04 5:03 kernel 3.6+ problem with Marvell 88SE9172 SATA Controller Davidovac Zoran
2013-10-06 1:00 ` Robert Hancock [this message]
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=5250B62E.4080407@gmail.com \
--to=hancockrwd@gmail.com \
--cc=davidovacz@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@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 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).