From: Brent Spillner <spillner@acm.org>
To: bhelgaas@google.com, tglx@linutronix.de, mingo@redhat.com,
bp@alien8.de, dave.hansen@linux.intel.com, x86@kernel.org,
hpa@zytor.com, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH] arch:x86:pci:irq.c: Improve log message when IRQ cannot be identified
Date: Fri, 28 Jan 2022 17:37:15 +0000 [thread overview]
Message-ID: <YfQpy5yGGqY8T0wW@jupiter.dyndns.org> (raw)
The existing code always suggests trying the pci=biosirq kernel
parameter, but this option is only recognized when CONFIG_PCI_BIOS is
set, which in turn depends on CONFIG_X86_32, so it is never appropriate
on x86_64.
The new version tries to form a more useful message when pci=biosirq is
not available, including by suggesting different acpi= options if
appropriate (probably the most common cause of failed IRQ discovery).
See arch/x86/pci/common.c:535 for the interpretation of pci=biosirq, and
arch/x86/Kconfig:2633 for the dependencies of CONFIG_PCI_BIOS.
Signed-off-by: Brent Spillner <spillner@acm.org>
---
arch/x86/pci/irq.c | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/arch/x86/pci/irq.c b/arch/x86/pci/irq.c
index 97b63e35e152..bc4aaaa74832 100644
--- a/arch/x86/pci/irq.c
+++ b/arch/x86/pci/irq.c
@@ -1522,7 +1522,21 @@ static int pirq_enable_irq(struct pci_dev *dev)
} else if (pci_probe & PCI_BIOS_IRQ_SCAN)
msg = "";
else
+#ifdef CONFIG_PCI_BIOS
msg = "; please try using pci=biosirq";
+#else
+ /* pci=biosirq is not a valid option */
+#ifdef CONFIG_ACPI
+ if (acpi_noirq)
+ msg = "; consider removing acpi=noirq";
+ else
+#endif
+ msg = "; recommend verifying UEFI/BIOS IRQ options"
+#ifndef CONFIG_ACPI
+ " or enabling ACPI"
+#endif
+ ;
+#endif
/*
* With IDE legacy devices the IRQ lookup failure is not
--
2.34.1
next reply other threads:[~2022-01-28 17:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 17:37 Brent Spillner [this message]
2022-01-28 18:00 ` [PATCH] arch:x86:pci:irq.c: Improve log message when IRQ cannot be identified Dave Hansen
2022-01-28 20:48 ` Brent Spillner
2022-01-28 21:36 ` Dave Hansen
2022-01-31 21:22 ` Bjorn Helgaas
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=YfQpy5yGGqY8T0wW@jupiter.dyndns.org \
--to=spillner@acm.org \
--cc=bhelgaas@google.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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 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).