From: no_spam@ntlworld.com
To: "Kathy Frazier" <kfrazier@mdc-dayton.com>, linux-kernel@vger.kernel.org
Subject: Re: Missing interrupts?
Date: Mon, 21 Jul 2003 21:00:54 +0100 [thread overview]
Message-ID: <200307212100.54433.no_spam@ntlworld.com> (raw)
In-Reply-To: <PMEMILJKPKGMMELCJCIGCEFOCDAA.kfrazier@mdc-dayton.com>
Kathy,
How did you check that the driver was asserting the interrupt? (do you have an
additional way of monitoring it?) I have yet to fully investigate my problem
and an additional tool to check if my board is actually asserting the
interrupt (and to find out how far it gets) would be very handy,
Thanks for the suggestions - more notes below
Thanks,
SA
> ">>"s truncated....
> Futhermore, it appears that things on the motherboard are is such a bad
> state, that no other interrupts are getting through (keyboard, mouse,
> network, etc). This same board and driver works fine in a Pentium 3
> system.
>
> >Machines test where everything worked: kernels 2.4.18-10 and 2.4.18-24.8.0
> > on athlon based PCs
> >
> >Machine where interrupts failed to appear: kernel 2.4.18-3 on a pentium 4.
>
> Are you running these tests using the same board? You might try moving the
> board for this device driver from the athlon PC to the pentium 4 PC just to
> insure it is not a problem with the board.
Same board each time
>...
>....
> Is the value in pi_stage.interrupt assigned from the irq element of the
> pci_dev structure (returned by pci_find_device routine)? This is the
> preferred way to obtain your IRQ rather than look directly at your device's
> config space.
I am currently inspecting the board config space - I will modify and test - is
it possible for the config space to be "wrong".
> Even though you are indicating that you will share the IRQ, have you tried
> adjusting BIOS settings or moving board to another slot to try to establish
> a unique IRQ for yourself? That would at least prevent another device
> driver from getting in your way.
The card and driver share "nicely" with a random assortment of hardware on the
"good" machines - I will try to get it a unique (or at least different
interrupt) on the bad machine (it current shares with usb on int 9 which
never seems to get any interrupts) and see how this pans out
> Just curious: Are you receiving any interrupts at all in the pentium 4
> system? Or is it running for awhile and then missing some? Does a missing
> interrupt hang your system?
The bad computer function fine in everyway except for the missing interrupts
from my card - the card and driver are robust in the sense that they can live
without the interrupts (performance can suffer though) so this problem is in
the category annoying and anomolous rather than fatal.
Ta SA.
next prev parent reply other threads:[~2003-07-21 19:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-21 16:20 Fwd: " Kathy Frazier
2003-07-21 20:00 ` no_spam [this message]
2003-07-22 13:06 ` Kathy Frazier
-- strict thread matches above, loose matches on Subject: below --
2003-07-18 15:51 SA
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=200307212100.54433.no_spam@ntlworld.com \
--to=no_spam@ntlworld.com \
--cc=kfrazier@mdc-dayton.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
all inboxes | Powered by JetHome®