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

Message-Id: <20081028.120419.252131562.davem@davemloft.net>
Date:	Tue, 28 Oct 2008 12:04:19 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	donner@...-breitband.de
Cc:	linux-kernel@...r.kernel.org, netdev@...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.

From: Marc Donner <donner@...-breitband.de>
Date: Tue, 28 Oct 2008 11:58:30 +0100

Please report networking problems to netdev@...r.kernel.org
(added to CC:)

Many networking developers do not read linux-kernel

> 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
> 
> Regards,
> 
> Marc
> 
> --
> 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/
--
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/