10402 2016-10-09 00:03:28 +0000 ACPI: No IRQ available for PCI Interrupt Link [LNKD]. Try pci=noacpi or acpi=off 2017-02-08 04:52:22 +0000 1 1 6 Yocto Project Subprojects Kernel linux-yocto 2.2 x86 x86 RESOLVED FIXED Medium+ normal 2.3 M3 1 net147 bruce.ashfield richard.purdie ross.burton sgw --- Regression (Used to work) No (bug/feature does not impact docs) oldest_to_newest 67078 0 net147 2016-10-09 00:03:28 +0000 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/ 67079 1 net147 2016-10-09 00:21:23 +0000 (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/ 67167 2 net147 2016-10-12 03:05:18 +0000 Patches have landed in linux-next: https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=dd6fd0e187654a991d824decfd24641276a2576c https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=c5924c1b5f290b8227e13627c95b73ac829a6845 https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=095095c2b9379d834dbd2fd8e42a2d1413a31eff 67296 3 bruce.ashfield 2016-10-17 15:01:35 +0000 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. 68450 4 net147 2016-11-20 12:16:02 +0000 Final patches have landed in mainline and backported to Linux 4.8.9. 68451 5 net147 2016-11-20 12:19:01 +0000 https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=86c711665c84dc4b37027be89223cfa0784cebc9 https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=6c76dd0c70662573615fd5aa4c3d0763da24d6e8 https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=a3f000ce7b4447a33569ea3cddc6b29cf90f740a 69672 6 bruce.ashfield 2017-01-10 20:33:37 +0000 Adding an estimate. will do this for 4.9 in M3. 70527 7 bruce.ashfield 2017-02-08 04:52:22 +0000 4.8-stable picked up these changes, and obviously 4.9+ has them as well. So we are covered on this issue.