Re: Interrupt fires when module is unloaded

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I have expanded on this a bit. I was not calling probe_irq_on() and probe_irq_off(). I am now wrapping the outb_p() calls:

mask = probe_irq_on(); 
outb_p() ....

val = probe_irq_off(mask);

My mask is 0x3c78 (11110001111000 binary) but val is 0. 

Behaviour is unchanged. 




On Mon, Jan 6, 2014 at 4:27 PM, Rajat Sharma <fs.rajat@xxxxxxxxx> wrote:
It would be nice to post the code when asking for debugging help. Looks like your interrupts are in masked state but when you unload the driver they are getting unmasked and hence you are receiving them on unload.

-Rajat


On Mon, Jan 6, 2014 at 4:09 PM, Eric Fowler <eric.fowler@xxxxxxxxx> wrote:
I am trying to figure out interrupts by writing a shadow of Rubini's 'short' program. Recall that Rubini tells us to enable parallel port interrupts by wiring pins 9&10 together, then writing binary data to the parallel port's address. 

I am doing that, but: 
- I don't see interrupts when I write to the port
- I do see one interrupt when I unload the driver (in the fop's .release method)
- This happens whether or not the pins are wired up. 

What is going on here?



_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@xxxxxxxxxxxxxxxxx
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies





--
cc:NSA
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@xxxxxxxxxxxxxxxxx
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux