From: Matthew Galgoci <mgalgoci@redhat.com>
To: linux-kernel@vger.kernel.org
Subject: cardbus pirq conflict
Date: Fri, 8 Dec 2000 13:01:48 -0500 [thread overview]
Message-ID: <20001208130148.B19712@redhat.com> (raw)
Hi Folks,
I am running the 2.4.0test12pre7 kernel on my laptop computer, and
I'm having some rather interesting problems.
For the longest time, usb never worked on this machine. As of the
happy patch that enabled bus mastering for usb controllers, it
magically started working. I am really happy that it does work
now.
The usb controller and the pcmcia bridge both share the same
irq, irq 10.
Now, my cardbus cards have stopped working. When I insert a cardbus
nic, I get the following message: "IRQ routing conflict in pirq
table! Try 'pci=autoirq'"
The card fails to initialize, and upon issuing the halt command, the
system generates a kernel Oops. I tend to think that the Oops is a
symptom of having a half initialized device. If anyone is interested,
I'll catch the Oops, run it though ksymoops, and send it to them.
If I try as the kernel suggests, and give the kernel options
pci=autoirq, there seems to be no noticable change.
If I switch to a isa^H^H^H I mean 16 bit version of the same ethernet
card, the card works find, and the usb controller works. As a matter
of fact, I've had the 16 bit nic and a usb nic both active at the
same time.
So, beyond reporting this and waiting for the next prepatch from Linus,
I really don't know where to go next. If I can provide anyone with more
information about the hardware or this problem, please ask.
Cheers!
--Matt Galgoci
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2000-12-08 18:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-08 18:01 Matthew Galgoci [this message]
2000-12-09 1:59 ` cardbus pirq conflict Andrew Morton
2000-12-11 17:48 ` Matthew Galgoci
2000-12-11 20:03 ` Matthew Galgoci
2000-12-11 20:30 ` Linus Torvalds
2000-12-11 20:55 ` Martin Mares
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=20001208130148.B19712@redhat.com \
--to=mgalgoci@redhat.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