From: Ondrej Zary <linux@rainbow-software.org>
To: linux-kernel@vger.kernel.org
Cc: linux-acpi@vger.kernel.org
Subject: 4.7 regression: ACPI: No IRQ available for PCI Interrupt Link [LNKD]. Try pci=noacpi or acpi=off
Date: Sun, 25 Sep 2016 15:12:05 +0200 [thread overview]
Message-ID: <201609251512.05657.linux@rainbow-software.org> (raw)
Hello,
I've upgraded kernel (Debian Squeeze - backports) from 4.6 (4.6.4-1~bpo8+1)
to 4.7 (4.7.2-1~bpo8+1) and IRQs stopped working with error messages like this:
ACPI: No IRQ available for PCI Interrupt Link [LNKD]. Try pci=noacpi or acpi=off
The same thing appeared on two different machines. Is it a known/fixed bug?
--
Ondrej Zary
next reply other threads:[~2016-09-25 13:18 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-25 13:12 Ondrej Zary [this message]
2016-09-26 12:23 ` 4.7 regression: ACPI: No IRQ available for PCI Interrupt Link [LNKD]. Try pci=noacpi or acpi=off Rafael J. Wysocki
2016-09-27 21:02 ` Ondrej Zary
2016-09-27 21:32 ` 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
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=201609251512.05657.linux@rainbow-software.org \
--to=linux@rainbow-software.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.