netdev - Re: Question about Mellanox FW reporting (incorrect) port types

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <509D698E.60000@redhat.com>
Date:	Fri, 09 Nov 2012 18:37:34 -0200
From:	Marcelo Ricardo Leitner <mleitner@...hat.com>
To:	Or Gerlitz <or.gerlitz@...il.com>
CC:	Yevgeny Petrilin <yevgenyp@...lanox.co.il>,
	netdev <netdev@...r.kernel.org>,
	Or Gerlitz <ogerlitz@...lanox.com>,
	Doug Ledford <dledford@...hat.com>,
	Yishai Hadas <yishaih@....mellanox.co.il>
Subject: Re: Question about Mellanox FW reporting (incorrect) port types

Em 17-10-2012 16:49, Marcelo Ricardo Leitner escreveu:
> On 10/17/2012 04:22 PM, Or Gerlitz wrote:
>> Marcelo Ricardo Leitner <mleitner@...hat.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.

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html