All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: Marc Donner <donner@dbd-breitband.de>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@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 17:30:15 -0600	[thread overview]
Message-ID: <4907A087.8070506@shaw.ca> (raw)
In-Reply-To: <fa.DGFAgeS7UIX09ggBLWLxaYf6hWE@ifi.uio.no>

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.

       reply	other threads:[~2008-10-28 23:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.DGFAgeS7UIX09ggBLWLxaYf6hWE@ifi.uio.no>
2008-10-28 23:30 ` Robert Hancock [this message]
2008-10-28 10:58 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
2008-10-28 19:04 ` David Miller
2008-10-28 20:29   ` Michael Chan

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=4907A087.8070506@shaw.ca \
    --to=hancockr@shaw.ca \
    --cc=donner@dbd-breitband.de \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.