From: Trent Piepho <tpiepho@impinj.com>
To: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"thesven73@gmail.com" <thesven73@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: No interrupt was generated using MSI
Date: Thu, 1 Nov 2018 21:35:31 +0000 [thread overview]
Message-ID: <1541108131.30311.181.camel@impinj.com> (raw)
In-Reply-To: <20181101213044.27844-1-TheSven73@googlemail.com>
On Thu, 2018-11-01 at 17:30 -0400, thesven73@gmail.com wrote:
> I am seeing this in my kernel log:
>
> [ 10.235625] tg3 0000:03:00.0 eth20: No interrupt was generated
> using MSI.
> Switching to INTx mode. Please report this failure to the PCI
> maintainer and include system chipset information
>
> I looked through MAINTAINERS, but I can't find the PCI maintainer.
> Can anyone help?
>
> Chipset info: this happens on a Freescale i.MX6Q. Mainline 4.19
> kernel.
> The devicetree entry for the pcie chipset is here:
>
> arch/arm/boot/dts/imx6qdl.dtsi:
>
> pcie: pcie@1ffc000 {
> compatible = "fsl,imx6q-pcie", "snps,dw-pcie";
> <snip>
> };
It sounds like you might be hitting the bug I posted a fix for
recently.
https://patchwork.kernel.org/patch/10657987/
prev parent reply other threads:[~2018-11-01 21:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-01 21:30 No interrupt was generated using MSI thesven73
2018-11-01 21:35 ` Trent Piepho [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=1541108131.30311.181.camel@impinj.com \
--to=tpiepho@impinj.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=thesven73@gmail.com \
/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