[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a12593c9-9ced-4bb8-b7a5-8247b08d0e0f@kernel.org>
Date: Wed, 27 Sep 2023 07:03:40 +0200
From: Jiri Slaby <jirislaby@...nel.org>
To: Takashi Sakamoto <o-takashi@...amocchi.jp>,
linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] firewire updates for 6.5-rc1
Hi,
On 26. 09. 23, 16:09, Takashi Sakamoto wrote:
> But in the reporter's environment:
>
> ```
> kernel: firewire_ohci 0000:22:00.0: enabling device (0080 -> 0083)
> kernel: firewire_ohci 0000:22:00.0: can't find IRQ for PCI INT A; please try using pci=biosirq
> kernel: genirq: Flags mismatch irq 0. 00000080 (firewire_ohci) vs. 00015a00 (timer)
> kernel: firewire_ohci 0000:22:00.0: failed to allocate interrupt 0
> kernel: firewire_ohci: probe of 0000:22:00.0 failed with error -16
> kernel: firewire_ohci 0000:22:00.0: removed fw-ohci device
Ah, that's why the system boots with acpi=noirq. It simply won't allow
the ohci driver to bind the device due to apparently wrong IRQ
configuration in the PCI device.
You can ignore this error, IMO. ACPI tables have the IRQs setup right
and those should be used (ie. acpi=noirq was used only for testing).
Let's chase the real problem (follow the bug).
thanks,
--
js
suse labs
Powered by blists - more mailing lists