From: Dhananjay Phadke <dhananjay.phadke@qlogic.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Jens Rosenboom <me@jayr.de>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Amit Salecha <amit.salecha@qlogic.com>,
Ameen Rahman <ameen.rahman@qlogic.com>
Subject: Re: [BUG] netxen: Stops working between 2.6.30 and 2.6.31-rc1
Date: Fri, 20 Nov 2009 09:30:28 -0800 [thread overview]
Message-ID: <4B06D234.4060600@qlogic.com> (raw)
In-Reply-To: <m1tywprvl4.fsf@fess.ebiederm.org>
> Weird. MSI's definitely weren't disabled. Looking a little farther at
> your quoted setup MSI work on your board. This is definitely
> something specific to the driver. Except for a few initialization
> races that are an issue for bonding I am running 2.6.31 just fine.
Jens,
Even if /proc/interrupt says PCI-MSI in both cases, single interrupt
case is msi vs. 4 vector case is msi-x. To confirm that msi-x doesn't
work with your card/machine, you can still stay on 2.6.31 and set
use_msi_x=0 in netxen_nic_main.c.
I had tried to make a available a module param to disable msi/msi-x for
platforms where msi-x doesn't work cleanly, but it was declined by David
Miller, et al.
Anyway, please note a few things -
Jens' has older generation (NX2031) of nic asic, so 4.0.xxx FW doesn't
apply:
NetXen XGb XFP Board S/N IF72MK0200 Chip rev 0x25
Eric has newer generation (NX3031) of nic asic:
NetXen Dual XGb SFP+ LP Board S/N SF86BK0008 Chip rev 0x41
Anyhow, what I learned here is Jens obtained firmware from IBM Japan.
Could you please describe the source of your device, you should involve
respective OEM (HP/IBM) for getting right revision of the firmware.
If it was purchased via direct channel, call QLogic support about
3.4.339 firmware. I can't imagine IBM Japan hosting firmware not
released for IBM branded NIC boards.
Thanks,
Dhananjay
next prev parent reply other threads:[~2009-11-20 17:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-19 16:39 [BUG] netxen: Stops working between 2.6.30 and 2.6.31-rc1 Jens Rosenboom
2009-11-19 18:07 ` Dhananjay Phadke
2009-11-19 18:36 ` Jens Rosenboom
2009-11-19 22:11 ` Dhananjay Phadke
2009-11-20 7:49 ` Jens Rosenboom
2009-11-20 16:11 ` Jens Rosenboom
2009-11-20 1:19 ` Eric W. Biederman
2009-11-20 7:52 ` Jens Rosenboom
2009-11-20 16:48 ` Eric W. Biederman
2009-11-20 17:30 ` Dhananjay Phadke [this message]
2009-11-20 17:43 ` Eric W. Biederman
2009-11-20 18:07 ` Dhananjay Phadke
2009-11-20 18:21 ` Eric W. Biederman
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=4B06D234.4060600@qlogic.com \
--to=dhananjay.phadke@qlogic.com \
--cc=ameen.rahman@qlogic.com \
--cc=amit.salecha@qlogic.com \
--cc=ebiederm@xmission.com \
--cc=me@jayr.de \
--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 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.