From: ebiederm@xmission.com (Eric W. Biederman)
To: Dhananjay Phadke <dhananjay.phadke@qlogic.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 10:21:05 -0800 [thread overview]
Message-ID: <m16395rram.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <4B06DAF9.6080108@qlogic.com> (Dhananjay Phadke's message of "Fri\, 20 Nov 2009 10\:07\:53 -0800")
Dhananjay Phadke <dhananjay.phadke@qlogic.com> writes:
> Eric W. Biederman wrote:
>> MSI-X uses the same messages on the wire is the same as MSI it is
>> only the programming interface that is different. So if MSI works and
>> MSI-X does not it is not a platform problem.
>>
>
> Sure, but firmware and driver see it differently. IMO, this points to some
> firmware issue (which is why I asked him to get right version from right
> source). All that driver did was tried to enable msi-x, from my testing, I can
> tell that both msi and msix work on all revisions of the nic asic, but firmware
> revision can make a difference. For chiprev 0x25, 3.4.339 is the right firmware
> version.
Sorry I meant that only as a clarification, not to derail the conversation.
This does sound like a firmware mismatch issue to me as well.
Eric
prev parent reply other threads:[~2009-11-20 18:21 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
2009-11-20 17:43 ` Eric W. Biederman
2009-11-20 18:07 ` Dhananjay Phadke
2009-11-20 18:21 ` Eric W. Biederman [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=m16395rram.fsf@fess.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=ameen.rahman@qlogic.com \
--cc=amit.salecha@qlogic.com \
--cc=dhananjay.phadke@qlogic.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 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).