>There is a possibility that you are trying to use a shared interrupt,
>but the IRQ is set up for edge. You can only share level interrupts.
I checked it out. The Edge/Level Triggered Register (ELCR) of Intel's 82801
ICH4 PIC register shows that our IRQ is setup for edge.
>Also, in the keyboard ISR, there is code that will spin <forever>
>if the bit that was supposed to be true when the interrupt occurred,
>remains false. This means that, if the timing was screwed up on some
>feature-board bus interface state-machine, it could corrupt what
>other devices see on the bus. The result could be a "hang forever"
>condition.
Hmmm, this is good information. Exactly what bit are you referring too? Is
this in /drivers/char/keyboard.c? I took a quick look through, but didn't
see anything. With the symptoms I am experiencing, I thought it might be
due to a piece of software spinning in a loop after it issued a cli.
However, I should at least see any pending interrupts in the IRR of the
8259! The cli would just prevent the CPU from being notified of the pending
interrupt.
>The 8259 is such an old device that all its bugs are known and
>work-arounds have been in-place for ages. It is unlikely that your
>problem has anything to do with either in 8259 or existing kernel
>code. My bet's on with a level/edge problem or bus corruption due
>to bus-contention (timing issues).
I tend to agree with you - the 8259 has been around forever. The snooping
I've done with my debug indicates that that the IRQ never gets through from
the hardware. The CPU is still running software and apparantly other things
are getting scheduled. But no other IRQs are getting through! Something is
corrupted on the bus. This posting was a final sanity check to insure I
wasn't totally out in left field with respect to the driver software. I
know there are issues of race conditions when using the sleep_on/wake_up
mechanisms. However, from what I've read, wait_event_interruptible() method
will avoid this . . . Any thoughts on that?
Thanks for your input!
Kathy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Jul 15 2003 - 22:00:58 EST