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] [day] [month] [year] [list]

Message-ID: <d12c1890909161730y663fe4f3s5b7e764a53d971ba@mail.gmail.com>
Date:	Wed, 16 Sep 2009 21:30:09 -0300
From:	Luis Fernando Planella Gonzalez <lfpg.dev@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: Re: Flooded by do_IRQ: 0.91 No irq handler for vector

Just to point out that I've upgraded to 2.6.31.0 and the bug is still there...
Just in case the problem is with the VIA board, is there anything
which can be done to try to debug?
--
Luis Fernando Planella Gonzalez

>> > Well, as I've installed sidux, it has upgraded the kernel to 2.6.30.5,
>> > but the error is the same.
>> > I've also tried:
>> > * noapic: the message changes to do_IRQ: 0.55 No irq handler for
>> > vector (irq -1), but then the X server fails to start
>>
>> Interesting...
>>
>> > * noacpi: have no effect on the error message.
>>
>> There is something very strange about your box.  Possibly it is
>> just VIA interrupt controller madness.  VIA has been known
>> to interrupt interrupt related fields in creative ways, and
>> we may be on the edge of another of these.
> Probably. My mother board is an Asus P5VD2-X, which is based on VIA PT890:
> http://br.asus.com/products.aspx?l1=3&l2=11&l3=346&l4=0&model=1362&modelmenu=1 (sorry, link in portuguese)
>
>>
>> I expect it is going to come down to writing a patch to dump out
>> all of the interrupt routing state on the system and to see what
>> is generating the totally unexpected interrupt and then to work our
>> way backwards from there.
>>
>> The fact that the vector number is changing indicates that it is
>> a programmable something that is causing the problem.
>>
>> I'm drawing a blank on which patch to write up.
>>
>> Eric
>>
> Thanks again.
>
> --
> Luis Fernando Planella Gonzalez
>
--
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/