From: Jiri Slaby <jirislaby@kernel.org>
To: Takashi Sakamoto <o-takashi@sakamocchi.jp>, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] firewire updates for 6.5-rc1
Date: Wed, 27 Sep 2023 07:03:40 +0200 [thread overview]
Message-ID: <a12593c9-9ced-4bb8-b7a5-8247b08d0e0f@kernel.org> (raw)
In-Reply-To: <20230926140922.GA6538@workstation.local>
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
next prev parent reply other threads:[~2023-09-27 5:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-04 12:18 Takashi Sakamoto
2023-07-04 18:38 ` pr-tracker-bot
2023-09-26 9:11 ` Jiri Slaby
2023-09-26 14:09 ` Takashi Sakamoto
2023-09-27 5:03 ` Jiri Slaby [this message]
2023-10-01 5:15 ` Takashi Sakamoto
2023-10-02 10:42 ` Jiri Slaby
2023-10-04 0:24 ` Takashi Sakamoto
2023-10-04 8:33 ` Jiri Slaby
2023-10-16 15:56 ` Takashi Sakamoto
2023-10-17 7:36 ` Jiri Slaby
2023-09-27 13:15 ` Linux regression tracking #adding (Thorsten Leemhuis)
2024-01-21 10:04 ` Linux regression tracking #update (Thorsten Leemhuis)
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=a12593c9-9ced-4bb8-b7a5-8247b08d0e0f@kernel.org \
--to=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=o-takashi@sakamocchi.jp \
/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
all inboxes | Powered by JetHome®