From: okaya@codeaurora.org
To: Ondrej Zary <linux@rainbow-software.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
linux-pci@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
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: Fri, 30 Sep 2016 09:14:42 -0400 [thread overview]
Message-ID: <677698369b23f5a6bcf3a66fed78802f@codeaurora.org> (raw)
In-Reply-To: <201609300844.24325.linux@rainbow-software.org>
On 2016-09-30 02:44, Ondrej Zary wrote:
> On Friday 30 September 2016, Sinan Kaya wrote:
>> On 9/29/2016 2:00 PM, Ondrej Zary wrote:
>> >> The previous two patches were in the right direction.
>> >>
>> >> > Can we also get the same output from 4.6 kernel with the attached
>> >> > patch for the same machine you sent these?
>> >
>> > Here it is.
>> >
>> >> > Something about SCI still doesn't feel right.
>> >> >
>> >> > The IRQ assignment fails if the penalty is greater than
>> >> > PIRQ_PENALTY_ISA_ALWAYS. This will happen if BIOS tells us to use an
>> >> > IRQ and same IRQ is in use by the SCI.
>>
>> Thanks, I reverted penalize_sci function and dropped patch #1. Can you
>> try
>> this again?
>
> It seems to work, at least on one machine.
Ok, that comfirms my suspicion. We are having trouble detecting sci
interrupt type and we end up penalizing the wrong value.
Can you try your other machines too?
I need to do some research now.
next prev parent reply other threads:[~2016-09-30 13:14 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 [this message]
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
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=677698369b23f5a6bcf3a66fed78802f@codeaurora.org \
--to=okaya@codeaurora.org \
--cc=bhelgaas@google.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux@rainbow-software.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).