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 for Android: free password hash cracker in your pocket

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

Message-ID: <20090831155800.GA2937@hack>
Date:	Mon, 31 Aug 2009 23:58:00 +0800
From:	Américo Wang <xiyou.wangcong@...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 Mon, Aug 10, 2009 at 08:30:08PM -0300, Luis Fernando Planella Gonzalez wrote:
>Hi.

Hi,

>I can't remember since when I've started seeing this, but since 2.6.23
>or 2.6.24, I think.
>Nowadays, I'm on Ubuntu 9.04, which is kernel 2.6.28.
>I'm flooded by the message: "do_IRQ: 0.91 No irq handler for vector"
>when in TTY.
>This is really annoying for text-base operation or in distros like
>sidux, where KDE watches syslog and shows a notification for every new
>line.
>Believe me, there are thousands of such notifications...
>Here is the dmesg results just after logging in:
>http://ubuntuforums.org/showpost.php?p=7759222&postcount=2 (yes, I've
>posted it in ubuntu forums with no succes ;)
>In this log, it's possible to see that the first time do_IRQ
>complains, it says: "do_IRQ: 0.99 No irq handler for vector". All
>others are for 0.91.
>I've tried adding the noirqbalance argument to kernel, and messed with
>everything related to IRQ in the BIOS with no success...
>Anybody, please help!!!

Hmm, I met a similar problem, on i386 2.6.29.

The more interesting thing is that the normal boot is fine but a kexec boot
will have this BUG_ON (about 50% chance), even 'irqpoll' doesn't help...

My guess is that maybe some driver failed to request_irq during kexec
boot, but I can't figure out which driver it is... Note, vector number
is 0x79.


-- 
Live like a child, think like the god.
 
--
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/