From: Ondrej Zary <linux@rainbow-software.org>
To: Sinan Kaya <okaya@codeaurora.org>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Bjorn Helgaas <bhelgaas@google.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Linux PCI <linux-pci@vger.kernel.org>,
wim@djo.tudelft.nl, ravikanth.nalla@hpe.com
Subject: Re: 4.7 regression: ACPI: No IRQ available for PCI Interrupt Link [LNKD]. Try pci=noacpi or acpi=off
Date: Tue, 4 Oct 2016 19:54:42 +0200 [thread overview]
Message-ID: <201610041954.45680.linux@rainbow-software.org> (raw)
In-Reply-To: <dda55738-d52b-1cdd-8973-8dea3506a835@codeaurora.org>
On Saturday 01 October 2016 19:49:17 Sinan Kaya wrote:
> On 9/30/2016 5:27 PM, Rafael J. Wysocki wrote:
> >>> >> What's the drawback, if any?
> >> >
> >> > I don't see any drawback to be honest.
> >
> > I'd go for it then, if Bjorn doesn't hate it.
>
> I posted a follow up patch a minute ago.
>
> [PATCH 1/3] Revert "ACPI,PCI,IRQ: reduce static IRQ array size to 16"
> [PATCH 2/3] ACPI, PCI IRQ: add PCI_USING penalty for ISA interrupts
> [PATCH 3/3] Revert "ACPI,PCI,IRQ: remove SCI penalize function"
>
> Can we have some testing coverage? and eventually have tested-by?
Fixes the problem on all 4 machines.
These patches also need to go into 4.7-stable and 4.8-stable.
Tested-by: Ondrej Zary <linux@rainbow-software.org>
--
Ondrej Zary
next prev parent reply other threads:[~2016-10-04 17:55 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201609251512.05657.linux@rainbow-software.org>
[not found] ` <2652205.dsh4NuQbCm@vostro.rjw.lan>
[not found] ` <201609272302.23765.linux@rainbow-software.org>
2016-09-27 21:32 ` 4.7 regression: ACPI: No IRQ available for PCI Interrupt Link [LNKD]. Try pci=noacpi or acpi=off Rafael J. Wysocki
2016-09-27 22:23 ` Ondrej Zary
2016-09-27 22:58 ` Rafael J. Wysocki
2016-09-27 23:06 ` Sinan Kaya
2016-09-28 8:32 ` Ondrej Zary
2016-09-28 14:11 ` Sinan Kaya
2016-09-28 17:02 ` Ondrej Zary
2016-09-28 18:22 ` Sinan Kaya
2016-09-28 19:23 ` Ondrej Zary
2016-09-28 23:38 ` Sinan Kaya
2016-09-29 9:10 ` Ondrej Zary
2016-09-29 13:09 ` okaya
2016-09-29 13:49 ` Ondrej Zary
2016-09-29 14:28 ` Sinan Kaya
2016-09-29 14:35 ` Sinan Kaya
2016-09-29 16:48 ` Ondrej Zary
2016-09-29 17:18 ` Sinan Kaya
2016-09-29 18:00 ` Ondrej Zary
2016-09-29 22:39 ` Sinan Kaya
2016-09-30 6:44 ` Ondrej Zary
2016-09-30 13:14 ` okaya
2016-09-30 15:56 ` Ondrej Zary
2016-09-30 19:30 ` Sinan Kaya
2016-09-30 19:39 ` Rafael J. Wysocki
2016-09-30 20:24 ` Sinan Kaya
2016-09-30 21:04 ` Rafael J. Wysocki
2016-09-30 21:14 ` Sinan Kaya
2016-09-30 21:27 ` Rafael J. Wysocki
2016-09-30 21:33 ` Sinan Kaya
2016-10-01 17:49 ` Sinan Kaya
2016-10-02 16:53 ` Ondrej Zary
2016-10-03 1:05 ` Sinan Kaya
2016-10-03 7:25 ` Ondrej Zary
2016-10-04 14:30 ` Sinan Kaya
2016-10-04 17:54 ` Ondrej Zary [this message]
2016-09-29 14:18 ` Wim Osterholt
2016-09-29 14:31 ` Sinan Kaya
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=201610041954.45680.linux@rainbow-software.org \
--to=linux@rainbow-software.org \
--cc=bhelgaas@google.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=okaya@codeaurora.org \
--cc=rafael@kernel.org \
--cc=ravikanth.nalla@hpe.com \
--cc=rjw@rjwysocki.net \
--cc=wim@djo.tudelft.nl \
/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).