From: SA <bullet.train@ntlworld.com>
To: linux-kernel@vger.kernel.org
Subject: Missing interrupts?
Date: Fri, 18 Jul 2003 16:51:21 +0100 [thread overview]
Message-ID: <200307181651.21730.bullet.train@ntlworld.com> (raw)
Dear LK,
I am testing a new device driver and have found that one one machine it does not receive any interrupts.
I am stumped by this problem and wonder if anyone had any advice before I start to take things apart blindly.
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.
I register the interrupt on open with
err=request_irq(pi_stage.interrupt,pi_int_handler,SA_SHIRQ,PI_IRQ_ID,(void*)&pi_stage);
My handler looks like
static void pi_int_handler(int irq, void *dev_id,struct pt_regs *regs){
u32 event;
pi_stage.ints_all++;
event=pi_read_control(PI_STAGE_INTEVENTSET);
if(event & PI_STAGE_ALLINTS){
pi_write_control(PI_STAGE_INTEVENTCLEAR,event &PI_STAGE_ALLINTS);
if(event & PI_STAGE_INTGPIO3)
pi_stage.ints_io++;
if(event & PI_STAGE_GPINT){
pi_stage.ints_axis++;
tasklet_schedule(&pi_tasklet);
}
pi_stage.ints_board++;
}
}
On the dodgy machine I see the driver and card working fine except for the missing interrupts.
The variable pi_stage.ints_all is never incremented and /proc/interrupts never reports any interrupts.
On all machines the conditions that generate the interrupts do occur.
It looks like on this one machine that interrupts are never received by the system.
Is it possible that differences between the BIOSs on the machines could cause this?
(ie my card is init'd differently so on the bad machine the ints are never generated or
received).
Any suggestions?
Thanks SA
next reply other threads:[~2003-07-18 16:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-18 15:51 SA [this message]
2003-07-21 16:20 Fwd: " Kathy Frazier
2003-07-21 20:00 ` no_spam
2003-07-22 13:06 ` Kathy Frazier
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=200307181651.21730.bullet.train@ntlworld.com \
--to=bullet.train@ntlworld.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®