From: Robert Hancock <hancockr@shaw.ca>
To: Nikos Chantziaras <realnc@arcor.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: do_IRQ: 0.83/0.84 No irq handler for vector
Date: Sun, 27 Jul 2008 13:43:42 -0600 [thread overview]
Message-ID: <488CCFEE.5040304@shaw.ca> (raw)
In-Reply-To: <fa.7GQkKKWUwuudcm81hY5cYLJkEY4@ifi.uio.no>
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?
next parent reply other threads:[~2008-07-27 19:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.dCDqP8nkXgM8NhJMm3I+bMK+//w@ifi.uio.no>
[not found] ` <fa.7GQkKKWUwuudcm81hY5cYLJkEY4@ifi.uio.no>
2008-07-27 19:43 ` Robert Hancock [this message]
2008-07-27 20:19 ` do_IRQ: 0.83/0.84 No irq handler for vector Nikos Chantziaras
2008-07-26 20:28 Nikos Chantziaras
2008-07-27 6:14 ` Nikos Chantziaras
2008-07-27 10:09 ` Nikos Chantziaras
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=488CCFEE.5040304@shaw.ca \
--to=hancockr@shaw.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=realnc@arcor.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox