A spurious interrupt is an interrupt the driver didn't expect.
Briefly, devices such as disks, parallel ports, serial ports, etc. use interrupts to signal back to the cpu that they have completed the last task given them or that the device has recieved data that the kernel needs to put away somewhere. The rationale behind this is that devides are very slow; you can hand them data, and there is room for thousands or even millions of other cpu instructions to be done before that device is ready to handle more data. Interrupts can also signal a need for attention: a serial port recieving characters sends interrupts letting the driver know that new data has arrived.
So a spurious interrupt is unexpected. You didn't give the damn thing any data, so why is it tapping you on the shoulder looking for attention? You could also have the case of an interrupt on a line that isn't configured at all: say the kernel hasn't been told of any device using interrupt 11, but whoops, there it is. That generates a different message, though.
Got something to add? Send me email.
More Articles by Tony Lawrence © 2011-07-05 Tony Lawrence
One day my daughter came in, looked over my shoulder at some Perl 4 code, and said, "What is that, swearing?" (Larry Wall)