mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: brian franklin <may26baf@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: free_irq problem in 2.6 kernel
Date: Fri, 29 Oct 2004 15:00:52 -0700 (PDT)	[thread overview]
Message-ID: <20041029220052.97805.qmail@web52601.mail.yahoo.com> (raw)

I have a network driver which uses PCI Interrupt D. 
Using kernel
2.6.8-1.528.2.10smp, I now have a problem when I call
free_irq().  It
now masks off the interrupt even though it is shared
with another
device.  My initial call to request_irq() succeeds,
and my driver will
correctly receive interrupts.  But once I call
free_irq(), the
interrupt is now masked, and subsequent calls to
request_irq() don't
unmask the interrupt.

The syntax of my calls to these two functions are:
status = request_irq(priv->irq , jnet_isr, SA_SHIRQ,
name1, dev);
and
free_irq(priv->irq, dev);

Can anyone shed some light on what I might be doing
wrong?

As a side note: I noticed that this kernel now
correctly configures
the IOAPIC configuration register with the interrupt
vector.  Previous
kernels did not.  Can anyone tell me how to
distinguish between a
kernel version that does configured the IOAPIC
configuration registers
correctly, and one that doesn't?  (In previous
versions, the
configuration register would have an interrupt vector
of IRQ169 while
the interrupt was really IRQ19.  Now, the interrupt
vector in the
configuration register matches with the IRQ that is
actually
selected.)

Thanks for any assistance.
Brian Franklin




		
__________________________________
Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish.
http://promotions.yahoo.com/new_mail 

             reply	other threads:[~2004-10-29 22:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-29 22:00 brian franklin [this message]
2004-10-30 23:09 ` Alan Cox

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=20041029220052.97805.qmail@web52601.mail.yahoo.com \
    --to=may26baf@yahoo.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®