From: "tj@kernel.org" <tj@kernel.org>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: "Shah, Nehal-bakulchandra" <Nehal-bakulchandra.Shah@amd.com>,
Bharat Kumar Gogada <bharat.kumar.gogada@xilinx.com>,
"Deucher, Alexander" <Alexander.Deucher@amd.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"holler@ahsoftware.de" <holler@ahsoftware.de>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Dan Williams <dan.j.williamps@intel.com>
Subject: Re: ATA failure regression
Date: Thu, 29 Sep 2016 13:33:11 +0200 [thread overview]
Message-ID: <20160929113311.GA26566@mtj.duckdns.org> (raw)
In-Reply-To: <20160929112558.GA24350@khazad-dum.debian.net>
Hello,
(cc'ing Dan, hi!)
On Thu, Sep 29, 2016 at 08:25:58AM -0300, Henrique de Moraes Holschuh wrote:
> Actually, according to Shah's post from the 26th to this thread,
> everything works just fine even with the IOMMU enabled, as long as the
> system is configured to NOT auto-shutdown unused SATA ports.
>
> That seems to give some extra avenues at fixing/working around the
> issue, maybe?
Hmm... it could be that the multiple msix routing gets screwed when
the bios disables unoccupied ports. Dan, can you please look into
this? Shah is seeing ahci failing during boot on an AMD platform with
msi enabled. If disabling of unoccupied ports is turned off in bios,
the problem goes away. Maybe we're mapping the irqs incorrectly in
such cases?
Thanks.
--
tejun
prev parent reply other threads:[~2016-09-29 11:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-23 9:25 ATA failure regression Shah, Nehal-bakulchandra
2016-09-23 10:10 ` Bharat Kumar Gogada
2016-09-26 10:15 ` Shah, Nehal-bakulchandra
2016-09-28 5:45 ` Shah, Nehal-bakulchandra
2016-09-29 8:22 ` tj
2016-09-29 11:25 ` Henrique de Moraes Holschuh
2016-09-29 11:33 ` tj [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=20160929113311.GA26566@mtj.duckdns.org \
--to=tj@kernel.org \
--cc=Alexander.Deucher@amd.com \
--cc=Nehal-bakulchandra.Shah@amd.com \
--cc=bharat.kumar.gogada@xilinx.com \
--cc=dan.j.williamps@intel.com \
--cc=hmh@hmh.eng.br \
--cc=holler@ahsoftware.de \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@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).