linux-kernel - Re: do_IRQ: 0.83/0.84 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-next>] [day] [month] [year] [list]

Date:	Sun, 27 Jul 2008 13:43:42 -0600
From:	Robert Hancock <hancockr@...w.ca>
To:	Nikos Chantziaras <realnc@...or.de>
CC:	linux-kernel@...r.kernel.org
Subject: Re: do_IRQ: 0.83/0.84 No irq handler for vector

Nikos Chantziaras wrote:
> Nikos Chantziaras wrote:
>> Kernel 2.6.26 (on x86-64) gives "do_IRQ: 0.83 No irq handler for 
>> vector" (and "do_IRQ: 0.83", but less often) warnings periodically.
> 
> I changed the kernel config:
> 
>   - CONFIG_PCI_MSI=y
>   + # CONFIG_PCI_MSI is not set
> 
> In other words I disabled Message Signaled Interrupt support.  Now 
> instead of "do_IRQ: 0.83 No irq handler for vector" I get:
> 
>   +------ PCI-Express Device Error ------+
>   Error Severity          : Uncorrected (Non-Fatal)
>   PCIE Bus Error type     : Transaction Layer
>   Flow Control Protocol   : First
>   Receiver ID             : 0010
>   VendorID=1106h, DeviceID=a208h, Bus=00h, Device=02h, Function=00h
>   Broadcast error_detected message
>   Broadcast mmio_enabled message
>   Broadcast resume message
>   AER driver successfully recovered
> 
> (Repeated as many times as the "do_IRQ" message previously.)
> 
> In case someone needs it, this is my complete dmesg:
> 
>   http://realnc.pastebin.com/d6534029
> 
> and this is the kernel configuration: 
> http://bugs.freedesktop.org/attachment.cgi?id=17912

My guess is some device is that some device is generating MSI interrupts 
without any handler being registered for it, and with MSI support 
disabled it now generates a master abort instead. Most likely whatever 
device is connected to the Bus=00h, Device=02h, Function=00h bridge. Can 
you post "lspci -vv" output?
--
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/