From: Sagi Grimberg <sagi@grimberg.me>
To: Or Gerlitz <gerlitz.or@gmail.com>
Cc: "linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
Leon Romanovsky <leon@kernel.org>,
Saeed Mahameed <saeedm@mellanox.com>,
Stable <stable@vger.kernel.org>,
Roy Shterman <roys@lightbitslabs.com>
Subject: Re: cx4 sriov problem in stable 4.14.47
Date: Wed, 20 Jun 2018 20:06:08 +0300 [thread overview]
Message-ID: <c74ce55f-e793-1bb2-fe4d-bbd815be4ab2@grimberg.me> (raw)
In-Reply-To: <CAJ3xEMhBueWttc8d_yi+rBCXgrsVUJQci9wEB-KP=OJ6ixur0Q@mail.gmail.com>
>> Hey folks,
>>
>> Seems that CX4 (Ethernet) sriov ports probe with link down in the latest
>> stable 4.14 kernel. I upgrated firmware but with no luck :(
>>
>> Has anyone seen this issue as well?
>>
>> Kernel: stable 4.14.47
>> Firmware: 12.22.1002
>> psid: MT_2140110033
>>
>> sysfs port state is DOWN and
>
> do you mean ip link on the pf shows link state down for the vf?
the PF is fine, the VF is down.
>> phys port state is Disabled.
>
> where do you see it is disabled and what happens if you take the PF
> netdev link up?
Nothing happens if I take it up, the carrier is off. I see the port
phys state via infiniband sysfs (which exposes it from the hca vport
context).
> We had a bug fix there recently [1] -- but it was for the switchdev
> mode not the legacy mode,
It was backported to 4,14 stable...
> are you using the switchdev mode? (if not, I recommend going there, the legacy
> mode is not going to last long)
No, I wasn't sure if it was mature enough in 4.14. And stable backports
don't always propagate immediately...
I'll try switchdev mode.
> Also, FWIW the whole ethernet sriov upstreaming is done in netdev, not rdma
I know, it should have went to netdev... Next time (which I hope won't
come too soon ;))
next prev parent reply other threads:[~2018-06-20 17:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-20 10:40 cx4 sriov problem in stable 4.14.47 Sagi Grimberg
2018-06-20 12:01 ` Leon Romanovsky
2018-06-20 12:28 ` Sagi Grimberg
2018-06-20 15:47 ` Or Gerlitz
2018-06-20 17:06 ` Sagi Grimberg [this message]
2018-06-21 7:05 ` Or Gerlitz
2018-06-20 18:44 ` Greg KH
2018-07-12 18:01 ` Or Gerlitz
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=c74ce55f-e793-1bb2-fe4d-bbd815be4ab2@grimberg.me \
--to=sagi@grimberg.me \
--cc=gerlitz.or@gmail.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=roys@lightbitslabs.com \
--cc=saeedm@mellanox.com \
--cc=stable@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).