From: Alan Kilian <kilian@bobodyne.com>
To: linux-kernel@vger.kernel.org
Subject: Help enabling PCI interrupts on Dell/SMP and Sun/SMP systems.
Date: Wed, 23 Feb 2005 14:24:33 -0600 [thread overview]
Message-ID: <1109190273.9116.307.camel@desk> (raw)
Folks,
This group was instrumental in helping me get my first-ever
linux/PCI-bus device driver working last year, and I'm back for
some more help if you are willing.
I have a PCI card that generates an interrupt when it completes
a DMA transfer to the PCs RAM.
This works just fine on a Dell 4400 running 2.6.10-1.766_FC3
When I try to run the driver on a Dell 2300 FC2/2.6.5-1.358smp
or a Sun W2100Z running FC2/2.6.10-1.14_FC2smp I can see the
DMA-done bit set in the device, but my interrupt service routine
never gets called.
On the Sun, I booted with "noapic" option, and it booted OK,
but then when my device generated an interrupt, there was a
kernel message about Disabling IRQ #5 and the system was hung
solidly.
I think this has something to do with the different interrupt
hardware on the more advanced servers compared to my desktop
Dell 4400, and I somehow need to "enable" the IOAPIC system
so that my interrupt gets through to my service routine, but I
don't know how.
I tried grepping through the kernel/drivers source, and I didn't
find anything that jumped out at me.
The Rubini drivers book didn't help in this area either,
although it's a wonderful book in other areas.
I can post source somewhere if it will help.
I can also post the essential bits from /var/log/messages about
all the incredibly complicated IOAPIC configuration stuff.
Thank you for your past help, and thank you in advance for any
tips you can provide.
-Alan
--
- Alan Kilian <kilian(at)bobodyne.com>
next reply other threads:[~2005-02-23 20:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-23 20:24 Alan Kilian [this message]
2005-02-23 20:46 ` Help enabling PCI interrupts on Dell/SMP and Sun/SMP systems linux-os
2005-02-23 22:17 ` Alan Kilian
2005-02-23 22:58 ` Peter Chubb
2005-02-23 23:24 ` Alan Kilian
2005-02-23 23:46 ` Roland Dreier
2005-02-24 1:23 ` Alan Kilian
2005-02-24 12:37 ` linux-os
[not found] <3Bbj7-7lG-17@gated-at.bofh.it>
[not found] ` <3BbMe-7FP-39@gated-at.bofh.it>
[not found] ` <3BdkS-GS-21@gated-at.bofh.it>
2005-02-23 23:25 ` Robert Hancock
[not found] ` <3BdNW-1bH-29@gated-at.bofh.it>
[not found] ` <3Be7p-1pY-43@gated-at.bofh.it>
2005-02-23 23:52 ` Robert Hancock
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=1109190273.9116.307.camel@desk \
--to=kilian@bobodyne.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.