RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1540012 - Cisco system add dpdk port to ovs bridge failed when configure mtu_request to be a jumbo frame
Summary: Cisco system add dpdk port to ovs bridge failed when configure mtu_request to...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: openvswitch
Version: 7.5
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: rc
: ---
Assignee: Aaron Conole
QA Contact: liting
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-30 05:29 UTC by liting
Modified: 2018-06-21 13:37 UTC (History)
7 users (show)

Fixed In Version: openvswitch-2.9.0-27.el7fdn
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-06-21 13:36:35 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
NIC settings exported from the cisco management tool (5.53 KB, text/plain)
2018-01-30 05:29 UTC, liting 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:1962 0 None None None 2018-06-21 13:37:49 UTC

Description liting 2018-01-30 05:29:42 UTC 
Created attachment 1388134 [details]
NIC settings exported from the cisco management tool

Description of problem:
Cisco system add dpdk port to ovs bridge failed when configure mtu_request to be a jumbo frame.

Version-Release number of selected component (if applicable):
openvswitch-2.9.0-0.1.20180108git8e3a28c.el7fdp.x86_64

How reproducible:


Steps to Reproduce:
1. Run following commands in cisco machine
driverctl -v set-override 0000:09:00.0 vfio-pci
driverctl -v set-override 0000:0a:00.0 vfio-pci

ovs-vsctl --no-wait set Open_vSwitch . other_config:dpdk-init=true
ovs-vsctl --no-wait set Open_vSwitch . other_config:dpdk-lcore-mask=0x1
ovs-vsctl --no-wait set Open_vSwitch . other_config:dpdk-socket-mem=4096,0
ovs-vsctl --timeout 10 set Open_vSwitch . other_config:max-idle=30000
systemctl restart openvswitch

ovs-vsctl --timeout 10 set Open_vSwitch . other_config:pmd-cpu-mask=0x20000200
ovs-vsctl --timeout 10 add-br br0 -- set bridge br0 datapath_type=netdev
ovs-vsctl --timeout 10 add-port br0 dpdk0 -- set Interface dpdk0 type=dpdk options:dpdk-devargs=0000:09:00.0 options:n_rxq=1 mtu_request=2000

2. Add dpdk1 without configure mtu_request to be a jumbo frame.
ovs-vsctl --timeout 10 add-port br0 dpdk1 -- set Interface dpdk1 type=dpdk options:dpdk-devargs=0000:0a:00.0 options:n_rxq=1


Actual results:
Run following command successfully.
ovs-vsctl --timeout 10 add-port br0 dpdk1 -- set Interface dpdk1 type=dpdk options:dpdk-devargs=0000:0a:00.0 options:n_rxq=1

But run following command failed.
ovs-vsctl --timeout 10 add-port br0 dpdk0 -- set Interface dpdk0 type=dpdk options:dpdk-devargs=0000:09:00.0 options:n_rxq=1 mtu_request=2000

check the /var/log/openvswitch/ovs-vswitchd.log
2018-01-29T07:35:34.486Z|00115|dpdk|INFO|EAL: PCI device 0000:09:00.0 on NUMA socket 0
2018-01-29T07:35:34.486Z|00116|dpdk|INFO|EAL:   probe driver: 1137:43 net_enic
2018-01-29T07:35:34.487Z|00117|dpdk|ERR|EAL: Cannot open /dev/vfio/55: Permission denied
2018-01-29T07:35:34.487Z|00118|dpdk|ERR|EAL: Driver cannot attach the device (0000:09:00.0)
2018-01-29T07:35:34.487Z|00119|netdev_dpdk|WARN|Error attaching device '0000:09:00.0' to DPDK
2018-01-29T07:35:34.487Z|00120|netdev|WARN|dpdk0: could not set configuration (Invalid argument)



Expected results:
Run following command successfully.
ovs-vsctl --timeout 10 add-port br0 dpdk0 -- set Interface dpdk0 type=dpdk options:dpdk-devargs=0000:09:00.0 options:n_rxq=1 mtu_request=2000

Additional info:
Following is the cisco nic info.
[root@cisco-c220m4-01 ~]# ethtool -i enp9s0
driver: enic
version: 2.3.0.42
firmware-version: 4.1(3a)
expansion-rom-version: 
bus-info: 0000:09:00.0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: no

[root@cisco-c220m4-01 ~]# lspci -s 0000:09:00.0
09:00.0 Ethernet controller: Cisco Systems Inc VIC Ethernet NIC (rev a2)

VIC model is VIC-1227
Comment 2 Aaron Conole 2018-01-30 13:11:49 UTC 
Can you give me access to the system?
Comment 5 Aaron Conole 2018-02-01 20:19:22 UTC 
Please capture the coredump from Open vSwitch when this occurs (I at least saw one happen when I looked).  I'll be able to debug.
Comment 7 Aaron Conole 2018-04-20 14:04:57 UTC 
The fix for this is upstream at:
  http://dpdk.org/ml/archives/dev/2018-April/095388.html

Waiting on it to be accepted.
Comment 8 Aaron Conole 2018-05-06 13:49:23 UTC 
This will be available in 2.9.0-27
Comment 13 errata-xmlrpc 2018-06-21 13:36:35 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:1962
Note You need to log in before you can comment on or make changes to this bug.