From: Thomas Gleixner <tglx@linutronix.de>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: Jiang Liu <jiang.liu@linux.intel.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Tony Luck <tony.luck@intel.com>, Joerg Roedel <joro@8bytes.org>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Grant Likely <grant.likely@linaro.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Bjorn Helgaas <bhelgaas@google.com>,
Randy Dunlap <rdunlap@infradead.org>,
Yinghai Lu <yinghai@kernel.org>, Len Brown <len.brown@intel.com>,
Pavel Machek <pavel@ucw.cz>,
linux-kernel@vger.kernel.org
Subject: Re: HT1000 SATA broken by "x86, irq, ACPI: Use common irqdomain map interface to program IOAPIC pins"
Date: Wed, 27 Aug 2014 23:24:15 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.10.1408272322130.3323@nanos> (raw)
In-Reply-To: <alpine.LRH.2.02.1408271657300.17705@file01.intranet.prod.int.rdu2.redhat.com>
On Wed, 27 Aug 2014, Mikulas Patocka wrote:
> Hi
>
> The patch d7b830013f59cf586c1cec3caa1ce7156da59a13, committed to 3.17-rc1,
> breaks the SATA controller (sata_svw driver) on HT1000 ServerWorks
> chipset. The other drivers work correctly.
>
> With the patch d7b830013f59cf586c1cec3caa1ce7156da59a13, the SATA
> controller times out after every command with lost interrupt.
>
> With the patch 16ee7b3dcc56be14b9a813612cff2cc2339cdced, the SATA driver
> can't be loaded at all, it fails with:
> sata_svw 0000:01:0e.0: version 2.3
> Failed to set pin attr for GSI11
> sata_svw 0000:01:0e.0: PCI INT A: failed to register GSI
> sata_svw: probe of 0000:01:0e.0 failed with error -1
Can you please pull
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/urgent
into your tree and check whether this solves the issues?
Thanks,
tglx
next prev parent reply other threads:[~2014-08-27 21:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-27 21:13 Mikulas Patocka
2014-08-27 21:24 ` Thomas Gleixner [this message]
2014-08-27 22:19 ` Mikulas Patocka
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=alpine.DEB.2.10.1408272322130.3323@nanos \
--to=tglx@linutronix.de \
--cc=benh@kernel.crashing.org \
--cc=bhelgaas@google.com \
--cc=grant.likely@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=jiang.liu@linux.intel.com \
--cc=joro@8bytes.org \
--cc=konrad.wilk@oracle.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=paul.gortmaker@windriver.com \
--cc=pavel@ucw.cz \
--cc=rdunlap@infradead.org \
--cc=rjw@rjwysocki.net \
--cc=tony.luck@intel.com \
--cc=yinghai@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®