From: Rajesh Shah <rajesh.shah@intel.com>
To: Nicolas Mailhot <nicolas.mailhot@laposte.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: pcie_portdrv_probe->Dev has invalid IRQ. Check vendor BIOS (CK804)
Date: Thu, 17 Nov 2005 15:27:04 -0800 [thread overview]
Message-ID: <20051117152704.B15853@unix-os.sc.intel.com> (raw)
In-Reply-To: <1130868315.2786.5.camel@rousalka.dyndns.org>; from nicolas.mailhot@laposte.net on Tue, Nov 01, 2005 at 10:05:14AM -0800
On Tue, Nov 01, 2005 at 10:05:14AM -0800, Nicolas Mailhot wrote:
>
> I've just booted on the last Fedora Devel kernel (2.6.14-1.1635_FC5,
> based on 2.6.14-git2) and my dmesg is now filled with:
>
> pcie_portdrv_probe->Dev has invalid IRQ. Check vendor BIOS
>
> messages.
>
> Should I worry ? Report it somewhere ? Attaching what info ?
>
I updated the corresponding bugzilla, repeating here for those
not watching bugzilla updates. This turned out to be a bogus
warning. The PCI express bridges on this machine do not
support any capabilities that require an interrupt (hotplug,
advanced error reporting). So, it's ok for the BIOS to not
report interrupt routing for the bridges.
I'll clean up the warning as part of the PCI express work I
expect to start soon.
Rajesh
prev parent reply other threads:[~2005-11-17 23:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-01 18:05 Nicolas Mailhot
2005-11-17 23:27 ` Rajesh Shah [this message]
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=20051117152704.B15853@unix-os.sc.intel.com \
--to=rajesh.shah@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.mailhot@laposte.net \
/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
Powered by JetHome