From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: "tj@kernel.org" <tj@kernel.org>
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>
Subject: Re: ATA failure regression
Date: Thu, 29 Sep 2016 08:25:58 -0300 [thread overview]
Message-ID: <20160929112558.GA24350@khazad-dum.debian.net> (raw)
In-Reply-To: <20160929082229.GA11087@mtj.duckdns.org>
On Thu, 29 Sep 2016, tj@kernel.org wrote:
> On Wed, Sep 28, 2016 at 05:45:08AM +0000, Shah, Nehal-bakulchandra wrote:
> > Can someone please help me to debug this issue?
>
> The only thing I can do from libata side is disbling msi on the
> affected platform, but the problem doesn't seem confined to ahci, so
> probably the right thing to do for now is disabling msi on the
> platform?
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?
--
Henrique Holschuh
next prev parent reply other threads:[~2016-09-29 11:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-23 9:25 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 [this message]
2016-09-29 11:33 ` tj
-- strict thread matches above, loose matches on Subject: below --
2016-09-22 7:08 Shah, Nehal-bakulchandra
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=20160929112558.GA24350@khazad-dum.debian.net \
--to=hmh@hmh.eng.br \
--cc=Alexander.Deucher@amd.com \
--cc=Nehal-bakulchandra.Shah@amd.com \
--cc=bharat.kumar.gogada@xilinx.com \
--cc=holler@ahsoftware.de \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@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
all inboxes | Powered by JetHome®