linux-kernel - Re: No interrupt was generated using MSI

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] [day] [month] [year] [list]

Message-ID: <1541108131.30311.181.camel@impinj.com>
Date:   Thu, 1 Nov 2018 21:35:31 +0000
From:   Trent Piepho <tpiepho@...inj.com>
To:     "linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
        "thesven73@...il.com" <thesven73@...il.com>
CC:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: No interrupt was generated using MSI

On Thu, 2018-11-01 at 17:30 -0400, thesven73@...il.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@...c000 {
> 	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/