Maybe you're right. My other idea is, since printk deals with console output, maybe if you are doing it inside an interrupt handler that directly or indirectly deal with console, then it will trigger oops.My understanding is that a *sleep* operation may cause block, but a *wake-up* operation never. And I heard that it is safe to invoke printk() in an interrupt handler. Of course not put printk() in __switch_to(), but that seems because of some other reason.
-- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/