From: Manfred Spraul <manfred@colorfullife.com>
To: linux-kernel@vger.kernel.org
Subject: Who sees "IRQ routing conflict" in dmesg?
Date: Mon, 05 Nov 2001 18:25:36 +0100 [thread overview]
Message-ID: <3BE6CB90.D08FB64C@colorfullife.com> (raw)
Who has a line
IRQ routing conflict for 01:23.4, have irq 5, want irq 6
in his dmesg dump?
If you find that line, please send me the relevant lines from the dmesg
dump, lspci -vx and cat /proc/interrupts. And obviously: does everything
work.
Thanks,
Manfred
Background:
Linux always uses the interrupts choosen by the bios. The bios stores
the irq number in PCI_INTERRUPT_LINE, and configures the irq router
accordingly.
If both do not match, then the above message is printed.
Right now the kernel uses the value from PCI_INTERRUPT_LINE, and ignores
the irq router.
That doesn't work with some vaio's, but before submitting that change to
Linus I want to verify that this won't break other setups.
next reply other threads:[~2001-11-05 17:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-05 17:25 Manfred Spraul [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-11-09 6:49 Who sees "IRQ routing conflict" in dmesg? Miles Lane
2001-11-11 1:35 ` Miles Lane
2001-11-12 9:21 ` Alan Cox
2001-12-14 15:22 ` Holger Lubitz
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=3BE6CB90.D08FB64C@colorfullife.com \
--to=manfred@colorfullife.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox