linux-kernel - Re: Flooded by do_IRQ: 0.91 No irq handler for vector

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4A835760.2050803@gmail.com>
Date:	Wed, 12 Aug 2009 17:59:28 -0600
From:	Robert Hancock <hancockrwd@...il.com>
To:	Luis Fernando Planella Gonzalez <lfpg.dev@...il.com>
CC:	linux-kernel@...r.kernel.org
Subject: Re: Flooded by do_IRQ: 0.91 No irq handler for vector

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..

>
>
>
> 2009/8/10 Luis Fernando Planella Gonzalez<lfpg.dev@...il.com>:
>> I've just compiled 2.6.30.4, and it shows another info:
>> do_IRQ: 0.91 No irq handler for vector (irq -1)
>>
>> Attached are the /proc/interrupts and the lspci -vv
>>
>> Anyway, sorry for not specifying my hardware:
>> * Intel Core2 Duo 2.13 GHz
>> * 2GB RAM
>> * NVidia 7900 GS
>>
>> Thanks.
>>

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/