From: Daniel Egger <degger@fhm.edu>
To: Heinz Diehl <hd@cavy.de>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: IRQ Routing Conflict
Date: 02 Nov 2002 00:42:34 +0100 [thread overview]
Message-ID: <1036194155.14932.17.camel@sonja.de.interearth.com> (raw)
In-Reply-To: <20021101223645.GA216@chiara.cavy.de>
[-- Attachment #1: Type: text/plain, Size: 955 bytes --]
Am Fre, 2002-11-01 um 23.36 schrieb Heinz Diehl:
> [....]
> 8139too Fast Ethernet driver 0.9.26
> PCI: Found IRQ 11 for device 00:11.0
> IRQ routing conflict for 00:11.0, have irq 10, want irq 11
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> Regardless of which PCI slot the card uses, the problem stays the same.
> I searched the net and found many people having the same trouble, but not a
> single solution for it.
Now that you mentioned it: Just a few hours ago I popped in a soundcard
into one of my machines:
Nov 1 16:10:20 nicole kernel: solo1: version v0.19 time 11:19:52 Apr 14 2002
Nov 1 16:10:20 nicole kernel: PCI: Found IRQ 10 for device 00:13.0
Nov 1 16:10:20 nicole kernel: IRQ routing conflict for 00:13.0, have irq 3, want irq 10
This is also an Apollo/MVP3 chipset. Other than that the soundcard seems
to work fine. I don't see this with any other card BTW.
--
Servus,
Daniel
[-- Attachment #2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2002-11-02 11:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-01 22:36 Heinz Diehl
2002-11-01 23:42 ` Daniel Egger [this message]
2002-11-07 19:53 ` Heinz Diehl
2002-11-09 9:30 ` Adrian Bunk
-- strict thread matches above, loose matches on Subject: below --
2002-01-23 10:58 IRQ routing conflict Marko Rauhamaa
2002-01-24 0:18 ` Erik Mouw
2002-01-24 10:43 ` Rob Landley
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=1036194155.14932.17.camel@sonja.de.interearth.com \
--to=degger@fhm.edu \
--cc=hd@cavy.de \
--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
Powered by JetHome