linux-kernel - Re: tg3:No interrupt was generated using MSI, switching to INTx mode. Please report this failure to the PCI maintainer and include system chipset information.

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

Message-ID: <4907A087.8070506@shaw.ca>
Date:	Tue, 28 Oct 2008 17:30:15 -0600
From:	Robert Hancock <hancockr@...w.ca>
To:	Marc Donner <donner@...-breitband.de>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: tg3:No interrupt was generated using MSI, switching to INTx mode.
 Please report this failure to the PCI maintainer and include system chipset
 information.

Marc Donner wrote:
> Hi @all,
> 
> we have installed a dual port Brodcam Gigabit Ethernet NIC, and get the
> following error in dmesg:
> 
> tg3: eth1 No interrupt was generated using MSI, switching to INTx mode.
> Please report this failure to the PCI maintainer and include system
> chipset information.
> 
> Who is responsible for this error message? We are using Kernel 2.6.21.1
> and the NIC Chipset is a Broadcom BCM5715CKPBG

Please post your full dmesg output from bootup, lspci -vvv output and 
what kind of motherboard or system you're using.

Also it would be useful to test a newer kernel to see if the problem 
still occurs. 2.6.21 is quite old these days.
--
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/