Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 30 Aug 2018 15:14:05 -0700
From:      Navdeep Parhar <np@FreeBSD.org>
To:        Marius Halden <marius.h@lden.org>, freebsd-net@freebsd.org
Subject:   Re: cxl nic not working after reboot
Message-ID:  <ba998b8e-d54c-667d-b0bb-8a6b7a566f05@FreeBSD.org>
In-Reply-To: <1535665888.3128528.1491873424.5CEF9F3A@webmail.messagingengine.com>
References:  <1535379569.2132387.1487489784.45227861@webmail.messagingengine.com> <20180827151302.GA10167@ox> <1535395530.234212.1487804896.64257978@webmail.messagingengine.com> <1535448912.3229649.1488521184.1EE83C33@webmail.messagingengine.com> <20180829062843.GA25476@ox> <1535538153.459716.1489861176.29777B66@webmail.messagingengine.com> <1535628110.3034153.1491191792.12397BCF@webmail.messagingengine.com> <8bb881ef-a701-1c94-3598-79a2724fa648@FreeBSD.org> <1535665888.3128528.1491873424.5CEF9F3A@webmail.messagingengine.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 8/30/18 2:51 PM, Marius Halden wrote:
> On Thu, Aug 30, 2018, at 19:27, Navdeep Parhar wrote:
>> On 8/30/18 4:21 AM, Marius Halden wrote:
>>> I tried to downgrade to a the previous bsdrp version we were running =
based on 11.1-RELEASE-p10, but it did not start working again. ifconfig o=
utput and t5nex0 devlog follows (non-working state), but it all looks fin=
e to me (media has always been reported wrong). I did notice though that =
"hw_mac_init_port[0], =E2=80=A6" will always be logged when it works but =
not when when it doesn't work. I confirmed this on a box still running th=
e old version which functions as intended.
>>>
>>> The ones not working has a newer firmware version than the ones worki=
ng.
>>>
>>> Non-working:
>>> # sysctl dev.t5nex.0.firmware_version
>>> dev.t5nex.0.firmware_version: 1.19.1.0
>>>
>>>
>>> Working:
>>> # sysctl dev.t5nex.0.firmware_version
>>> dev.t5nex.0.firmware_version: 1.16.45.0
>>>
>>> Any other ideas?
>>>
>>
>> I'm still looking into it.  The current working theory is that the pee=
r
>> is trying to autonegotiate when it shouldn't (it's 1Gbps optics).  If
>> you know how to disable AN on the peer this should be easy to test.
>=20
> Thanks. Unfortunately we don't have access to the peer as that's our IS=
Ps router. According to the sysctl autonegotiate is not supported on our =
side.
>=20

I'll get a couple of 1G optics in a day or so and then I'll be able to
try some things for myself.  Wait for that or try a 1G TWINAX (copper)
SFP+ cable in case you have one -- that should be able to link up (if
it's really autonegotiation that's causing problems).

Regards,
Navdeep




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ba998b8e-d54c-667d-b0bb-8a6b7a566f05>