Messages in this thread | | | From | (Eric W. Biederman) | Date | Wed, 19 Aug 2009 11:39:38 -0700 | Subject | Re: Flooded by do_IRQ: 0.91 No irq handler for vector |
| |
Robert Hancock <hancockrwd@gmail.com> writes:
> On 08/11/2009 04:28 PM, Luis Fernando Planella Gonzalez wrote: >> I'm really concerned that all those interrupts might slow down the >> computer somehow... >> Here is an attached syslog part after a reboot. >> Sometimes, the ratelimit says that thousands of callbacks were suppressed. >> Is there a way to make this message be displayed only once? >> >> In arch/x86/kernel/irq.c, the line 213 is: >> irq = __get_cpu_var(vector_irq)[vector]; >> >> In my case, the returned irq is -1. Doesn't it makes sense to not log >> the "No irq handler for vector" message when irq< 0? >> >> Or even a deeper answer: Why, in my case, the resulting irq is -1? > > Not logging would just cover up the problem, the issue in your case is that > something seems to be asserting a ton of interrupts on an IRQ line that no > driver has claimed..
It is slightly worse. We are seeing interrupts asserted and we don't know which IRQ line they belong to. This should never happen.
You say it is first 0.99 and 0.91 so it is moving.
Luis are you running a 64bit kernel? I think you would have to be for your symptoms to go all of the way back to 2.6.24.
My primary suspect is that something the irq migration code is not working properly on your computer. Could you disable /usr/sbin/irqbalance (possibly just by deleting it) and tell me if that fixes your symptoms?
If not we have a very nasty bug in how your ioapics are being programmed.
Eric
| |