No, the "scheduling in interrupt" doesn't imply that you tried to wake
something up in the interrupt - it means that something had to sleep in
the interrupt handler, which in turn forces a re-schedule, which is why
you get the message.
One classic reason for this is if you're reading from (or writing to)
user land from the interrupt: this is a no-no, as the user pages may be
paged out and thus the system needs to page it in (and sleep).
There are other ways you can trigger the message: if your interrupt
handler dies with an oops, the interrupt counts will be corrupted, and
the next scheduling will be unhappy (but then you really shoul dhave
seen an oops too).
Or if you call something from your interrupt handler that can sleep.
Like allocating memory without the GFP_ATOMIC flag, or doing a "down()",
or any number of things that imply a re-schedule.
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu