From: "Michael Chan" <mchan@broadcom.com>
To: "David Miller" <davem@davemloft.net>
Cc: "donner@dbd-breitband.de" <donner@dbd-breitband.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.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.
Date: Tue, 28 Oct 2008 13:29:20 -0700 [thread overview]
Message-ID: <1225225760.9170.59.camel@HP1> (raw)
In-Reply-To: <20081028.120419.252131562.davem@davemloft.net>
On Tue, 2008-10-28 at 12:04 -0700, David Miller wrote:
> From: Marc Donner <donner@dbd-breitband.de>
> Date: Tue, 28 Oct 2008 11:58:30 +0100
>
> Please report networking problems to netdev@vger.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
> >
This message means that your system chipset (not the NIC) does not
support MSI. Please provide lspci -vvv to show the system chipset on
your system. Thanks.
prev parent reply other threads:[~2008-10-28 20:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1225191510.26840.6.camel@localhost>
2008-10-28 19:04 ` tg3:No interrupt was generated using MSI, switching to INTx mode. Please report this failure to the PCI maintainer and include system chipset information David Miller
2008-10-28 20:29 ` Michael Chan [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=1225225760.9170.59.camel@HP1 \
--to=mchan@broadcom.com \
--cc=davem@davemloft.net \
--cc=donner@dbd-breitband.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).