Bug 1379946
Summary: | Linux 4.7: No IRQ available for PCI Interrupt Link | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Frank Mehnert <frank.mehnert> |
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 24 | CC: | gansalmon, ichavero, itamar, jonathan, kernel-maint, madhu.chinakonda, mchehab, michael.thayer, volpial3 |
Target Milestone: | --- | Flags: | jforbes:
needinfo?
|
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-04-28 17:24:01 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Frank Mehnert
2016-09-28 08:15:43 UTC
Typo: Of course the kernel message is "ACPI: No IRQ available for PCI Interrupt Link [LNKD]. Try pci=noacpi or acpi=off". See drivers/acpi/pci_link.c function acpi_pci_link_allocate(). We have done a bit of further analysis. It is indeed acpi_irq_get_penalty() preventing sharing because irq_get_trigger_type() returns zero. However, that is incorrect because the ACPI specification requires the SCI to be a level-triggered, active-low interrupt, shareable with PCI devices. We suspect that the ACPI code fails to convey the SCI type information during initialization in the case where there's no I/O APIC and no MADT. When an I/O APIC and MADT are in place, the routine acpi_sci_ioapic_setup() in arch/x86/kernel/acpi/boot.c appears to do the work of setting the SCI type. Rafael Wysocki told me that this is will be fixed "for 4.9-rc1 and 4.8.y/4.7.y". We found what we presume to be the relevant patchwork discussion<1>. We will confirm when we have tested an updated kernel. <1> https://patchwork.kernel.org/patch/9357253/ *********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 24 kernel bugs. Fedora 25 has now been rebased to 4.10.9-100.fc24. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 26, and are still experiencing this issue, please change the version to Fedora 26. If you experience different issues, please open a new bug report for those. *********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously. |