patches for DPDK stable branches
 help / color / mirror / Atom feed
From: "Zijie Pan" <zijie.pan@6wind.com>
To: stable <stable@dpdk.org>
Cc: yliu <yliu@fridaylinux.org>, "david.marchand" <david.marchand@6wind.com>
Subject: [dpdk-stable] Port of mlx5 can not start after setting link-down on dpdk-stable v17.11.2
Date: Thu, 31 May 2018 17:47:37 +0800	[thread overview]
Message-ID: <tencent_4B4450D650BECF4E3C1B920E@qq.com> (raw)

Hi commit authors (and maintainers),

Please help to backport patches to fix following issue. 
Here are the steps of testpmd on dpdk-17.11.2:
testpmd> show port info 0

********************* Infos for port 0  *********************
MAC address: E4:1D:2D:E7:0C:FA
Driver name: net_mlx5
Connect to socket: 0
...

testpmd> set link-down port 0
testpmd> 
Port 0: LSC event

testpmd> port stop 0
Stopping ports...
Checking link statuses...
Done
testpmd> port start 0
PMD: net_mlx5: Forcing port 0 link to be up
Fail to start port 0
Please stop the ports first
Done
<== Fail to start the port.

Test is OK if using master of dpdk:
testpmd> set link-down port 0
testpmd> 
Port 0: LSC event

testpmd> port stop 0
Stopping ports...
Checking link statuses...
Done
testpmd> port start 0
Port 0: E4:1D:2D:E7:0C:FA
Checking link statuses...
Done
<== Port can start successfully.

This issue was introduced by following commits:
322e1ce net/mlx5: fix link state on device start
f1e3e97 net/mlx5: fix handling link status event

This issue was fixed with following commit from dpdk (master):
7ba5320 net/mlx5: fix link status behavior

The related patches should be ported into dpdk-stable v17.11.2.

Thanks,
Zijie

             reply	other threads:[~2018-05-31  9:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-31  9:47 Zijie Pan [this message]
2018-06-02  4:42 ` Yuanhan Liu

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=tencent_4B4450D650BECF4E3C1B920E@qq.com \
    --to=zijie.pan@6wind.com \
    --cc=david.marchand@6wind.com \
    --cc=stable@dpdk.org \
    --cc=yliu@fridaylinux.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).