From: Bjorn Helgaas <bhelgaas@google.com>
To: bugzilla-daemon@bugzilla.kernel.org
Cc: linux-pci@vger.kernel.org, Michael Chan <mchan@broadcom.com>
Subject: Re: [Bug 50671] New: bnx2: No interrupt was generated using MSI, switching to INTx mode
Date: Thu, 6 Dec 2012 17:33:54 -0700 [thread overview]
Message-ID: <CAErSpo4gfmt97canuW4x48+-v2kfXiED0rukQvCNOdrQUuJ73g@mail.gmail.com> (raw)
In-Reply-To: <bug-50671-41252@https.bugzilla.kernel.org/>
> https://bugzilla.kernel.org/show_bug.cgi?id=50671
> When booting 3.6.5 on a Proliant DL360 G3, I get this in dmesg:
>
> bnx2: Broadcom NetXtreme II Gigabit Ethernet Driver bnx2 v2.2.3 (June 27,
> 2012)
> bnx2 0000:01:01.0: eth0: HP NC370F Multifunction Gigabit Server Adapter (A2)
> PCI-X 64-bit 100MHz found at mem f4000000, IRQ 28
> bnx2 0000:01:01.0: irq 80 for MSI/MSI-X
> bnx2 0000:01:01.0: eth2: No interrupt was generated using MSI, switching to
> INTx mode. Please report this failure to the PCI maintainer and include system
> chipset information.
The DL360 G3 is pretty ancient. The HP NC370F quickspecs
(http://h18004.www1.hp.com/products/quickspecs/12196_na/12196_na.html)
say it is supported on the DL360 G4, G4p, and G5, but not the G3. I
have no idea why.
I assume the NC370F has never been able to use MSI on this box with any kernel?
We have quirks that disable MSI globally on some machines; maybe we
need to do that on this system as well.
Can you attach a complete dmesg log and output of "lspci -vv"?
parent reply other threads:[~2012-12-07 0:34 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <bug-50671-41252@https.bugzilla.kernel.org/>]
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=CAErSpo4gfmt97canuW4x48+-v2kfXiED0rukQvCNOdrQUuJ73g@mail.gmail.com \
--to=bhelgaas@google.com \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mchan@broadcom.com \
/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).