All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Ricardo Leitner <mleitner@redhat.com>
To: Or Gerlitz <or.gerlitz@gmail.com>
Cc: Yevgeny Petrilin <yevgenyp@mellanox.co.il>,
	netdev <netdev@vger.kernel.org>,
	Or Gerlitz <ogerlitz@mellanox.com>,
	Doug Ledford <dledford@redhat.com>,
	Yishai Hadas <yishaih@dev.mellanox.co.il>
Subject: Re: Question about Mellanox FW reporting (incorrect) port types
Date: Fri, 09 Nov 2012 18:37:34 -0200	[thread overview]
Message-ID: <509D698E.60000@redhat.com> (raw)
In-Reply-To: <507F0BD5.7080005@redhat.com>

Em 17-10-2012 16:49, Marcelo Ricardo Leitner escreveu:
> On 10/17/2012 04:22 PM, Or Gerlitz wrote:
>> Marcelo Ricardo Leitner <mleitner@redhat.com> wrote:
>>>
>>> [...] So my questions are: is it possible to the firmware report a
>>> wrong port type like
>>> that? Is it somehow configurable by sysadmin (via fw update, ..), can
>>> we flip that byte
>>> or is it a manufacturing issue?

For completeness,

As it happens the customer had the HP Infinband Enablement Kit 
(614841-B21) installed at jumper location 53 (J53) of the motherboard, 
which makes the QSFP port of the S390s' NC543i interface an Infiniband 
interface rather than a 10gbE interface. Removing this allowed the port 
to be brought-up as 10GbE just fine.

Interesting that it worked as 10GbE even with InifiniBand Enablement Kit 
on it, so the port was just advertised, but not forced, as InfiniBand. 
Or something like that.

Thanks,
Marcelo.

      reply	other threads:[~2012-11-09 20:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-17 16:27 Question about Mellanox FW reporting (incorrect) port types Marcelo Ricardo Leitner
2012-10-17 19:22 ` Or Gerlitz
2012-10-17 19:49   ` Marcelo Ricardo Leitner
2012-11-09 20:37     ` Marcelo Ricardo Leitner [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=509D698E.60000@redhat.com \
    --to=mleitner@redhat.com \
    --cc=dledford@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=ogerlitz@mellanox.com \
    --cc=or.gerlitz@gmail.com \
    --cc=yevgenyp@mellanox.co.il \
    --cc=yishaih@dev.mellanox.co.il \
    /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.