On 30.09.2014, Ranjan Maitra wrote:
Thanks! I will do that right now. This only happens to me on a
wakeup
from hibernate and with one new laptop (Dell Precision M3800).
If this gives you problems, you could try to disable irqbalance to
work around. Otherwise, I would have ignored the message (which is
kind of a warning, if I remember the source correctly - there were
hard lockups some years ago, and AFAIR the code around the missing
interrupt for a certain cpu vector (take a look into irq.c) was
modified to ack the missing interrupt, giving the system a chance to
proceed. Feel free to correct me if I'm wrong.