Bug 10402 - ACPI: No IRQ available for PCI Interrupt Link [LNKD]. Try pci=noacpi or acpi=off
Summary: ACPI: No IRQ available for PCI Interrupt Link [LNKD]. Try pci=noacpi or acpi=off
Status: RESOLVED FIXED
Alias: None
Product: Kernel
Classification: Yocto Project Subprojects
Component: linux-yocto (show other bugs)
Version: 2.2
Hardware: x86 x86
: Medium+ normal
Target Milestone: 2.3 M3
Assignee: Bruce Ashfield
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2016-10-09 00:03 UTC by Jonathan Liu
Modified: 2017-02-08 04:52 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: Regression (Used to work)
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jonathan Liu 2016-10-09 00:03:28 UTC 
Booting qemux86 kernel in VirtualBox 32-bit guest with 4 network adapters emulating Intel PRO/1000 MT Desktop (82540EM) can result in the following in the kernel log:
ACPI: No IRQ available for PCI Interrupt Link [LNKD]. Try pci=noacpi or acpi=off

As a result, one or more network adapters will not work and will be missing the RUNNNING status in the ifconfig output.

This regression was introduced in Linux 4.6.0 with 103544d86976338057d6a91f721b49d3acc7df7f and affects all releases after.

It is fixed by the following patches pending review:
https://patchwork.kernel.org/patch/9362309/
https://patchwork.kernel.org/patch/9362295/
https://patchwork.kernel.org/patch/9362303/
Comment 1 Jonathan Liu 2016-10-09 00:21:23 UTC 
(In reply to comment #0)
> Booting qemux86 kernel in VirtualBox 32-bit guest with 4 network adapters
> emulating Intel PRO/1000 MT Desktop (82540EM) can result in the following in
> the kernel log:
> ACPI: No IRQ available for PCI Interrupt Link [LNKD]. Try pci=noacpi or
> acpi=off
> 
> As a result, one or more network adapters will not work and will be missing
> the RUNNNING status in the ifconfig output.
> 
> This regression was introduced in Linux 4.6.0 with
> 103544d86976338057d6a91f721b49d3acc7df7f and affects all releases after.

Introduced in Linux 4.7.0 actually. Works fine in 4.6.0.

> 
> It is fixed by the following patches pending review:
> https://patchwork.kernel.org/patch/9362309/
> https://patchwork.kernel.org/patch/9362295/
> https://patchwork.kernel.org/patch/9362303/
Comment 3 Bruce Ashfield 2016-10-17 15:01:35 UTC 
And I see that this is now popped off linux-next and being re-worked.

If something final makes it into a tree in the next few days, I'll grab the
change, otherwise, I'm doing to do these merges post 2.2 release.

I'm updating the priority of the bug as such.
Comment 4 Jonathan Liu 2016-11-20 12:16:02 UTC 
Final patches have landed in mainline and backported to Linux 4.8.9.
Comment 6 Bruce Ashfield 2017-01-10 20:33:37 UTC 
Adding an estimate. will do this for 4.9 in M3.
Comment 7 Bruce Ashfield 2017-02-08 04:52:22 UTC 
4.8-stable picked up these changes, and obviously 4.9+ has them as well. So we are covered on this issue.