[Bug 1851446] Re: Backport MPLS patches from 5.3 to 4.15

Hi Jeff. Unfortunately, was missing patch [1] that add the expose the support in the mlx5 driver. [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.5-rc2=5dc9520bf04a6b95660a307d7654460d1463d91a could you please add it ? Yours, Talat -- You received this bug

[Bug 1801574] Re: [cosmic] ipoib ping with large message size failed

Hi, After trying the steps that mentioned in #4 on 18.10, the issue doesn't reproduces with the suggested setting. yours, Talat -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801574 Title

[Bug 1801574] Re: [cosmic] ipoib ping with large message size failed

Hi Sure i will try it and update. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801574 Title: [cosmic] ipoib ping with large message size failed To manage notifications about this bug go to:

[Bug 1801574] Re: [cosmic] ipoib ping with large message size failed

Hi Tyler, We did a kernel bisecting and we fount that the mentioned commit is the root cause of this big, if bionic contain this commit, so the bug also in bionic release. yours, Talat -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu

[Bug 1801574] [NEW] [cosmic] ipoib ping with large message size failed

Public bug reported: We see that ping over ipoib interface stuck with large packets, this is a new degradation, this test pass on Ubuntu 18.04. After investigating the issue, we see that commit [1] introduce the issue, and it is not an upstream commit, it is canonical commit. Could you please

[Bug 1799049] Re: [bionic]mlx5: reading SW stats through ifstat cause kernel crash

The patch fixes the issue and we tested it. Thanks, Talat -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799049 Title: [bionic]mlx5: reading SW stats through ifstat cause kernel crash To manage

[Bug 1799049] Re: [bionic]mlx5: reading SW stats through ifstat cause kernel crash

Thank you for your concern. I already sent the patch to the canonical kernel mailing list, and waiting for them to review it. Thanks, Talat -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799049

[Bug 1799397] [NEW] [dpdk]rte_memcpy() moves data incorrectly on Ubuntu 18.04 on Intel Skylake.

Public bug reported: Hi, Christian We've recently encountered a weird issue with Ubuntu 18.04 on the Skylake server. I can always reproduce this crash and I could narrowed it down. I guess it could be a GCC issue. [1] How to reproduce - ConnectX-4Lx/ConnectX-5 with mlx5 PMD in DPDK 18.02.1 -

[Bug 1799049] [NEW] [bionic]mlx5: reading SW stats through ifstat cause kernel crash

Public bug reported: Description of problem: Attempting to read SW stats (ifstat -x cpu_hit) on a system with probed VFs will crash the system. How reproducible: Always Steps to Reproduce: 1. Create a VF echo 1 > /sys/bus/pci/devices/\:82\:00.0/sriov_numvfs 2. read SW stats: ifstat -x

[Bug 1783775] [NEW] [bionic] qemu-* depends on libibverbs

Public bug reported: During OFED internal installation the [1] packages removed due to libibverbs1 package dependencies, for example [2]. We see that qemu-system-x86 is depends on libibverbs1 as we see in the apt-case [2] Once the qemu-* are deleted, we can't work over virtualization (VM,

[Bug 1764982] Re: [bionic] machine stuck and bonding not working well when nvmet_rdma module is loaded

** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764982 Title: [bionic] machine stuck and bonding not working well

[Bug 1764982] Re: [bionic] machine stuck and bonding not working well when nvmet_rdma module is loaded

Hi, Sorry I missed that, will do it today. yours, Talat -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764982 Title: [bionic] machine stuck and bonding not working well when nvmet_rdma module

[Bug 1774132] Re: [Bionic]udev stop notifying when network interface added

Thank you Dima, Added requested files. yours, Talat -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1774132 Title: [Bionic]udev stop notifying when network interface added To manage notifications

[Bug 1774132] Re: [Bionic]udev stop notifying when network interface added

** Attachment added: "dmesg" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1774132/+attachment/5146405/+files/dmesgub18.04.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1774132

[Bug 1774132] Re: [Bionic]udev stop notifying when network interface added

** Attachment added: "udevadm" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1774132/+attachment/5146404/+files/udevadm18.04.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1774132

[Bug 1774132] [NEW] [Bionic]udev stop notifying when network interface added

Public bug reported: Expected: After a network driver restart, the network interfaces are deleted and added again, the udev should notify that new interface was added. then the interface service should be started accordingly. Actual: Udev doesn't notify about that new interface is added and the

[Bug 1770964] [NEW] [Bionic][RSS][ConnectX5]:testpmd stop receiving the packets after restarting the ports

Public bug reported: How to reproduce: Start testpmd using the following command: testpmd -n 4 -w 00:06.0,mprq_en=0,rx_vec_en=0,tx_vec_en=0 -w 00:07.0,mprq_en=0,rx_vec_en=0,tx_vec_en=0 -- --burst=64 --mbcache=512 -i --nb-cores=11 --txd=1024 --rxd=1024 --disable-hw-vlan-strip --forward-

[Bug 1764982] Re: [bionic] machine stuck and bonding not working well when nvmet_rdma module is loaded

Thank you for the build, I tested with those patches and it is work. Thanks, Talat -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764982 Title: [bionic] machine stuck and bonding not working well

[Bug 1764982] [NEW] [bionic] machine stuck and bonding not working well when nvmet_rdma module is loaded

Public bug reported: Hi Machine stuck after unregistering bonding interface when the nvmet_rdma module is loading. scenario: # modprobe nvmet_rdma # modprobe -r bonding # modprobe bonding -v mode=1 miimon=100 fail_over_mac=0 # ifdown eth4 # ifdown eth5 # ip addr add 15.209.12.173/8

[Bug 1763325] Re: [bionic] ConnectX5 Large message size throughput degradation in TCP

Testing this patch with bionic and it is working properly before the patch # ethtool --show-priv-flags enp6s0f0 Private flags for enp6s0f0: rx_cqe_moder : on tx_cqe_moder : on

[Bug 1763325] [NEW] [bionic] ConnectX5 Large message size throughput degradation in TCP

Public bug reported: we see degradation ~20% on ConnectX-5/4 in the following case: TCP, 1 QP, 1 stream, unidir, single port. Message sizes 1M and up show this degradation. After changing the default TX moderation mode to off we see up to 40% packet rate and up to 23% bandwidth degradtions.

[Bug 1763269] [NEW] Mellanox [mlx5] [bionic] UBSAN: Undefined behaviour in ./include/linux/net_dim.h

Public bug reported: We see UBSAN: Undefined behaviour in ./include/linux/net_dim.h:243:6 we saw the following trace during traffic in the regression: [12885.292500] UBSAN: Undefined behaviour in ./include/linux/net_dim.h:243:6 [12885.296358] signed integer overflow: [12885.300100] 358869104 *

[Bug 1758662] Re: [Bionic] mlx4 ETH - mlnx_qos failed when set some TC to vendor

After testing the build, the issue didn't reproduced. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758662 Title: [Bionic] mlx4 ETH - mlnx_qos failed when set some TC to vendor To manage

[Bug 1758662] Re: [Bionic] mlx4 ETH - mlnx_qos failed when set some TC to vendor

Thank you, will test and update. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758662 Title: [Bionic] mlx4 ETH - mlnx_qos failed when set some TC to vendor To manage notifications about this bug

[Bug 1758662] [NEW] [Bionic] mlx4 ETH - mlnx_qos failed when set some TC to vendor

Public bug reported: reproduce: [root@reg-l-vrt-41018-010 ~]# /usr/bin/mlnx_qos -i ens8 -s vendor,ets,vendor,ets,ets,strict,ets,vendor -t 0,36,0,55,4,0,5,0 Netlink error: Bad value. see dmesg. [root@reg-l-vrt-41018-010 ~]# dmesg [69718.992299] mlx4_en: ens8: TC[0]: Not supported TSA: 255

[Bug 1747170] Re: installer no ipv4 dhcp

Hi, Is there any workaround for this issue? Yours, Talat -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747170 Title: installer no ipv4 dhcp To manage notifications about this bug go to: https

[Bug 1719302] Re: Please include mlx4 and mlx5 InfiniBand modules

Hi Luke, Any update with this bug? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1719302 Title: Please include mlx4 and mlx5 InfiniBand modules To manage notifications about this bug go to:

[Bug 1732892] Re: [MIR] 18.04 rdma-core as replacement for older ibverbs code

Hi, please note that need to remove the mlx4.conf from the kmod package. Opened a bug on this issue LP: #1693503 yours, Talat -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1732892 Title: [MIR

[Bug 1732892] Re: [MIR] 18.04 rdma-core as replacement for older ibverbs code

to report bugs and submit patches. please note that there are many static analyzers and one can choose the specific tool to be used. We see great importance to integrate rdma-core into Ubuntu for the technical and business wise. Yours, Talat -- You received this bug notification because you

[Bug 1732892] Re: [MIR] 18.04 rdma-core as replacement for older ibverbs code

Hi, Any update with rdma-core ? Yours, Talat -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1732892 Title: [MIR] 18.04 rdma-core as replacement for older ibverbs code To manage notifications

[Bug 1715319] [NEW] [IPV6] DHCP client gets 128 subnet mask instead of any other that defined

Public bug reported: After configuring DHCP server (with and without RADVD), the client gets ipv6 address in range that was defined, or preserved. But the subnetmask of the address is 128 no matter what was the definition. Steps to reproduce 1.Install packages: #apt-get install -y *dhcp*

[Bug 1693503] Re: Remove mlx4.conf

ok, could you please just change the name of the file ? I will do a tests next week to figure if mlx4_core request the modules mlx_en when the link type is ETh, then we don't need this file at all. thanks Talat -- You received this bug notification because you are a member of Ubuntu Bugs

[Bug 1701892] [NEW] [Artful] mlx5e-Introduce RX Page-Reuse

Public bug reported: This feature is a Page-Reuse mechanism in non-Striding RQ RX datapath. A WQE (RX descriptor) buffer is a page, that in most cases was fully wasted on a packet that is much smaller, requiring a new page for the next round. In this feature, we implement a page-reuse mechanism,

[Bug 1693503] [NEW] Remove mlx4.conf

/modprobe.d/libmlx4.conf” that will come with “rdma-core” package, and prevents running a script (/sbin/mlx4-setup.sh) that configures ConnectX-3 devices port types (IB vs. ETH). thanks Talat ** Affects: kmod (Ubuntu) Importance: Undecided Status: New -- You received this bug

[Bug 1687877] Re: bonding - mlx5 - speed changed to 0 after changing ring size

Thank you, Tested it and it fixes the issue. could you please add this fix to the next SRU -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1687877 Title: bonding - mlx5 - speed changed to 0 after

[Bug 1687877] [NEW] bonding - mlx5 - speed changed to 0 after changing ring size

enp66s0f1 [268312.732089] bond0: link status up again after 0 ms for interface enp66s0f1 the upstream commit "bonding: allow notifications for bond_set_slave_link_state " fix the issue, will cherry-pick and send to xenial git tree. Thanks, Talat ** Affects: linux (Ubuntu) Importance:

[Bug 1682418] Re: [zesty] mlx5 OVS vxlan ipv6 LNST test cause Oops

Additional trace with this test is below [80921.628988] general protection fault: [#1] SMP [80921.630449] Modules linked in: act_mirred act_tunnel_key cls_flower sch_ingress vport_vxlan vxlan ip6_udp_tunnel udp_tunnel vfio_pci vfio_iommu_type1 vfio_virqfd vfio mlx5_ib ib_core openvswitch

[Bug 1678585] Re: [Zesty] TSO doesn't work properly

It is working with Ubuntu 16.10 . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1678585 Title: [Zesty] TSO doesn't work properly To manage notifications about this bug go to:

[Bug 1678585] Re: [Zesty] TSO doesn't work properly

Hi, This test work properly in the previous releases. Thanks, Talat -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1678585 Title: [Zesty] TSO doesn't work properly To manage notifications about

[Bug 1682418] [NEW] [zesty] mlx5 OVS vxlan ipv6 LNST test cause Oops

3. enable 2 VM's on the mlnx5 Physical Function on each machine 4. setup lnst on vm and HV (run lnst-slave) 5. run IPv VXLAN lnst test in loop for example #lnst-ctl -d --pools=talat run recipes/ovs_offload/1_virt_ovs_vxlan_ipv6.xml Call trace kernel: [76406.381439] Oop

[Bug 1681344] [NEW] Ping interface to its IP failed using -I option

packet loss, time 9200ms Tested with driver mlx4 / mlx5 / e1000 iputils version iputils-ping3:20161105-1ubuntu2 Thanks, Talat ** Affects: iputils (Ubuntu) Importance: Undecided Status: New ** Description changed: Scenario: - $ifconfig + $ifconfig

[Bug 1678585] Re: [Zesty] TSO doesn't work properly

Unfortunately, No. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1678585 Title: [Zesty] TSO doesn't work properly To manage notifications about this bug go to:

[Bug 1678585] Re: [Zesty] TSO doesn't work properly

The bug is exist also in kernel that mentioned in commit#2 4.11.0-041100rc5-generic ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1678585 Title: [Zesty]

[Bug 1678585] [NEW] [Zesty] TSO doesn't work properly

Public bug reported: The TSO (TCP segmentation offload), By default it is shown to be ON, but actually aggregation doesn’t happen. When turning it on again - aggregation is observed. Same behavior for mlx4_en, mlx5_core, igb. Steps to repro: 1. root:~# uname -r 4.10.0-14-generic 2. root:~#

[Bug 1668042] Re: [Xenial - 16.04 ]Bonding driver - stack corruption when trying to copy 20 bytes to a sockaddr

Thanks, Tested and the fix is working properly. Talat ** Tags removed: verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668042 Title: [Xenial - 16.04 ]Bonding driver

[Bug 1676786] Re: [Zesty] mlx5_core Kernel oops with bonding mode 1 and 6

This commit fix the issue commit e497ec680c4cd51e76bfcdd49363d9ab8d32a757 Author: Talat Batheesh <tal...@mellanox.com> Date: Tue Mar 28 16:13:41 2017 +0300 net/mlx5: Avoid dereferencing uninitialized pointer In NETDEV_CHANGEUPPER event the upper_info field is valid onl

[Bug 1676858] [NEW] [zesty] mlx4_core OOM with 32 bit arch

Public bug reported: we get OOM when we load the mlx4_core driver with 32-bit system with rich cpus machines The following upstream patches will fix this issue 3608b13 mlx4: reduce OOM risk on arches with large pages ** Affects: linux (Ubuntu) Importance: Undecided Status: New

[Bug 1676857] [NEW] [zesty] mlx4_core OOM with 32 bit arch

Public bug reported: we get OOM when we load the mlx4_core driver with 32-bit system with rich cpus machines The following upstream patches will fix this issue acd7628 mlx4: reduce rx ring page_cache size 3608b13 mlx4: reduce OOM risk on arches with large pages ** Affects: linux (Ubuntu)

[Bug 1676388] Re: [zesty] mlx5e OVS fixes

Additional patches that needed, I will send them to the mailing list as well 375f51e net/mlx5: E-Switch, Don't allow changing inline mode when flows are configured d85cdcc net/mlx5e: Change the TC offload rule add/del code path to be per NIC or E-Switch 4456f61 devlink: allow to fillup eswitch

[Bug 1676786] [NEW] [Zesty] mlx5_core Kernel oops with bonding mode 1 and 6

l send it also to canonical kernel team mailing list. Thanks, Talat ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1

[Bug 1676388] [NEW] [zesty] mlx5e OVS fixes

Public bug reported: We see the following issues with Ubuntu Zesty while testing the OVS offloading. I already test the patches that fix this issue and i'm going to send them to kernel-t...@lists.canonical.com Issues 1. FW error of groups overlapping when scaling up ovs tc qdisc del dev

[Bug 1672144] Re: ifup service of network device stay active after driver stop

The issue doesn't reproduce with the 4.10.5 mainline kernel. could you please cherry-pick this commit to the zesty kernel? Thanks Talat -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1672144 Title

[Bug 1672144] Re: ifup service of network device stay active after driver stop

Thank you I will give a try and update. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1672144 Title: ifup service of network device stay active after driver stop To manage notifications

[Bug 1672144] Re: ifup service of network device stay active after driver stop

# service is up although the network interface doesn't exist. This issue not reproduced with kernel 4.9. when we moved to kernel 4.10 we see this issue. thanks Talat -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net

[Bug 1672144] Re: ifup service of network device stay active after driver stop

network interface ifup. # ifup -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1672144 Title: ifup service of network device stay active after driver stop To manage notifications about this bug go

[Bug 1673491] Re: [Zesty] libnl3 Segmentation fault in sriov environments

Thank you , The update is passed and libnl updated to libnl-3-200:amd64 (3.2.29-0ubuntu2). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1673491 Title: [Zesty] libnl3 Segmentation fault in sriov

[Bug 1672144] Re: ifup service of network device stay active after driver stop

No, not equal :~# systemctl cat sys-subsystem-net-devices-ens1f0.device No files found for sys-subsystem-net-devices-ens1f0.device. :~# ifup ens1f0 ifup: interface ens1f0 already configured :~# systemctl cat ifup@ens1f0.service # /lib/systemd/system/ifup@.service [Unit] Description=ifup for %I

[Bug 1674087] Re: [zesty] net sched actions - Adding support for user cookies

The patches sent to kernel-t...@lists.canonical.com Thanks, Talat -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1674087 Title: [zesty] net sched actions - Adding support for user cookies

[Bug 1674087] [NEW] [zesty] net sched actions - Adding support for user cookies

Public bug reported: Adding optional 128-bit action cookie. The idea is to save user state that when retrieved serves as a correlator. The kernel _should not_ interpret it. The user can store whatever they wish in the 128 bits like persistent data, http or existing kernel fib protocol field,

[Bug 1673491] Re: [Zesty] libnl3 Segmentation fault in sriov environments

Thank you, The fix is working, i validate it with machine that has sriov environment. Dimitri, could you please add this fixes to the zesty release ? Thanks, Talat -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https

[Bug 1673491] Re: [Zesty] libvirtd Segmentation fault after running virt-manager

Hi, Thanks for taking a look at the bug and taking the time to help improve the package. This issue is a show stopper for our products, I would appreciate it if you would prepare a package with the fix that we can test and verify the fix. Thanks, Talat -- You received this bug notification

[Bug 1673491] [NEW] [Zesty] libvirtd Segmentation fault after running virt-manager

Public bug reported: in Ubuntu 17.04 we can't open a virt-manager, we see sefault This issue happen when we update from kernel 4.10.0-9-generic to 4.10.0-11-generic root@:~# /usr/sbin/libvirtd Segmentation fault (core dumped) root@:~# gdb /usr/sbin/libvirtd ./core GNU

[Bug 1672144] [NEW] ifup service of network device stay active after driver stop

Public bug reported: The network device systemd service stay active after unload the module of this network device, that call close port (ndo_stop). once we try to load the NIC driver again, it try to start the ifup service of his NICs and due to the service is already up, so it fail and we

[Bug 1669317] Re: iproute2: range error adding rules from tc

This Bug invalid due to iproute 4.9.0 doesn't support Matching Arp. ** Changed in: iproute2 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1669317 Title:

[Bug 1669317] Re: iproute2: range error adding rules from tc

** Patch added: "tc fix" https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1669317/+attachment/4829659/+files/0001-tc-flower-Fix-parsing-ip-address.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1669317] [NEW] iproute2: range error adding rules from tc

Public bug reported: Trying to add a rule from tc resulted in an ERANGE error example: # tc filter add dev ens5f0_0 protocol ip parent : flower skip_hw dst_mac e4:11:22:11:4a:51 src_mac e4:11:22:11:4a:50 ip_proto tcp src_ip 1.1.1.1 dst_ip 2.2.2.2 action drop

[Bug 1668042] Re: [Xenial - 16.04 ]Bonding driver - stack corruption when trying to copy 20 bytes to a sockaddr

Thank you, the fix works as expected in Xenial. ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668042 Title: [Xenial - 16.04 ]Bonding driver - stack corruption

[Bug 1668042] Re: [Xenial - 16.04 ]Bonding driver - stack corruption when trying to copy 20 bytes to a sockaddr

Could you please add this fix also to trusty? ** Also affects: linux-lts-trusty (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-lts-trusty (Ubuntu) ** No longer affects: linux-lts-trusty (Ubuntu Xenial) -- You received this bug notification because you are a

[Bug 1668019] Re: [UBUNTU Zesty] mlx5 - Improve OVS offload driver

The patches already sent to kernel-t...@lists.canonical.com. Thanks, Talat -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668019 Title: [UBUNTU Zesty] mlx5 - Improve OVS offload driver To manage

[Bug 1668042] Re: [Xenial - 16.04 ]Bonding driver - stack corruption when trying to copy 20 bytes to a sockaddr

Thank you, will test and update. By the way, i sent the patch to kernel-t...@lists.canonical.com. Thank you, Talat -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668042 Title: [Xenial - 16.04

[Bug 1668042] [NEW] [Xenial - 16.04 ]Bonding driver - stack corruption when trying to copy 20 bytes to a sockaddr

Public bug reported: In Ubuntu Xenial with kernel 4.4.0-65, we get kernel Panic after scenario [1]. patch [2] should fix the issue When using an IPoIB bond currently only active-backup mode is a valid use case and this commit strengthens it. Since commit 2ab82852a270

[Bug 1668019] [NEW] [UBUNTU Zesty] mlx5 - Improve OVS offload driver

Public bug reported: The patches in this series should improve the OVS offloading driver and some fixes mlx5 driver, by adding reflect HW offload status for querying whether a filter is offloaded to HW or not. This patches is already accepted upstream net-next (4.11). The following patches

[Bug 1649207] Re: mlx5_core failed to increase rx ring to 4096 - SIOCSIFFLAGS: Cannot allocate memory

** Tags added: yakkety -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1649207 Title: mlx5_core failed to increase rx ring to 4096 - SIOCSIFFLAGS: Cannot allocate memory To manage notifications

[Bug 1649207] [NEW] mlx5_core failed to increase rx ring to 4096 - SIOCSIFFLAGS: Cannot allocate memory

3608ae77c098 net/mlx5e: Move function mlx5e_create_umr_mkey 1c1b522808a1 net/mlx5e: Implement Fragmented Work Queue (WQ) Thanks, Talat ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: patch -- You received this bug notification because you are a member of Ubuntu Bugs

[Bug 1634862] Re: PPC + kernel 4.8 swap_dup: Bad swap file entry 2c0000000016ed28

Hi, we didn't see the issue on kernel 4.8.0-27-generic. do we have fixes that related to this area in kernel 4.8.0-27-generic? thanks, Talat -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1634862

[Bug 1634862] Re: PPC + kernel 4.8 swap_dup: Bad swap file entry 2c0000000016ed28

Hi, Any update with this bug ? thanks, Talat -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1634862 Title: PPC + kernel 4.8 swap_dup: Bad swap file entry 2c16ed28 To manage notifications

[Bug 1638256] [NEW] ifup fail when use MTU small than 68

Public bug reported: ifup failed when we set a static MTU small than 68, and when we change the static configuration and try to run ifdown and then ifup, the interface still with the old MTU and both of ifup and ifdown command fail. when we change the MTU manually by ip tool and then change it

[Bug 1634862] Re: PPC + kernel 4.8 swap_dup: Bad swap file entry 2c0000000016ed28

v4.9-rc2 http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9-rc2/ not working Thanks, Talat -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1634862 Title: PPC + kernel 4.8 swap_dup: Bad swap file entry

[Bug 1634862] Re: PPC + kernel 4.8 swap_dup: Bad swap file entry 2c0000000016ed28

Hi, there is no ppc image under http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9-rc1/, the ppc page not found. as we see there " Build for ppc64el failed (see BUILD.LOG.ppc64el): linux-headers-4.9.0-040900rc1_4.9.0-040900rc1.201610151630_all.deb *_ppc64el.deb " Thanks Tala

[Bug 1634862] [NEW] PPC + kernel 4.8 swap_dup: Bad swap file entry 2c0000000016ed28

Public bug reported: Hi on ppc machines with Ubuntu 16.10 (Yakkety Yak), after upgrading to last Ubuntu kernel (4.8), and running installation of MLNX_OFED Driver package that run a compilation jobs that equal to number of CPUs , the System hangs and we got a bad swap file message with pages

[Bug 1565649] Re: add support for architectures ppc64el arm64

Hi Brian, could you please update about the progress of this bug ? thanks, Talat -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1565649 Title: add support for architectures ppc64el arm64

[Bug 1477466] Re: Low performance when using vlan over VxLan

Hi, We will test this scenario on the latest Ubuntu (Yakkety Yak). this may take a time, will update later. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1477466 Title: Low performance when using

[Bug 1477466] Re: Low performance when using vlan over VxLan

Hi Dragan, This is an old bug, as far as i remember that we tested it and the performance still not as expected. we can test it again, but does this patches back-ported ? thanks, Talat -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu

[Bug 1585978] Re: mlx5_core kexec fail

** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1585978 Title: mlx5_core kexec fail To manage notifications about

[Bug 1528466] Re: Mellanox ConnectX4 MTU limits: max and min

** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1528466 Title: Mellanox ConnectX4 MTU limits: max and min To

[Bug 1585978] [NEW] mlx5_core kexec fail

Public bug reported: In machine with ConnectX4 device the kexec failed load a new kernel. missing pci shutdown callback. Operation system - Ubuntu 16.04 kernel 4.4.0-22-generic Scenario # kexec -l /boot/vmlinuz-4.3.0-rc6-gemini-perf-2015-10-22_19-44-01

[Bug 1115710] Re: Mellanox mlx4_en network driver is not automatically loaded

libexec/mlx4-setup.sh -a -f /etc/rdma/mlx4.conf ]; then /usr/libexec/mlx4-setup.sh < /etc/rdma/mlx4.conf; fi; /sbin/modprobe mlx4_en; /sbin/modprobe mlx4_ib) this should load the diver with the requested port type configuration. could you please revert this fix? Thanks, Talat -- You recei

[Bug 1544978] Re: PCI Call Traces hw csum failure in dmesg with 4.4.0-2-generic

Hi, This upstream commit should fix the bug commit 82d69203df634b4dfa765c94f60ce9482bcc44d6 Author: Daniel Jurgens Date: Wed May 4 15:00:33 2016 +0300 net/mlx4_en: Fix endianness bug in IPV6 csum calculation Use htons instead of unconditionally byte swapping

[Bug 1577164] Re: mstflint stop working 4.1.0+1.46.gb1cdaf7-1ubuntu3_amd64.deb

Thank you, Working properly. BR, Talat ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1577164 Title: mstflint stop working

[Bug 1577164] [NEW] mstflint stop working 4.1.0+1.46.gb1cdaf7-1ubuntu3_amd64.deb

Public bug reported: Hi, After the last update, mstflint stop working. The installation didn't install the script. # apt-get install mstflint Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: mstflint 0

[Bug 1470167] Re: mstflint doesn't support Mellanox ConnectX-4 HCAs

** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1470167 Title: mstflint doesn't support Mellanox ConnectX-4 HCAs To manage

[Bug 1470167] Re: mstflint doesn't support Mellanox ConnectX-4 HCAs

Great, Many thanks. Tested on Ubuntu 15.10(Wily) and Ubuntu 14.04.4(Trusty), it is working properly. Thanks, Talat -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1470167 Title: mstflint doesn't

[Bug 1565650] [NEW] add support for architectures ppc64el arm64

Public bug reported: Hi, could you please add support for Architectures ppc64el arm64. Thanks, Talat ** Affects: libibcm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https

[Bug 1565649] [NEW] add support for architectures ppc64el arm64

Public bug reported: Hi, could you please add support for Architectures ppc64el arm64. Thanks, Talat ** Affects: srptools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu

[Bug 1529815] Re: InfiniBand DHCP flow with PRA and DHCP relay not working

Hi Rafael, Thank you for the great job. The Broadcast flag is working, the packet drop was in the switch. We will ask our costumer to install this PPA, will update later. Thank you, Talat -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed

[Bug 1557950] [NEW] mlx5_core kernel trace after "ethtool -C eth1 adaptive-rx on" flow

Public bug reported: reproduce steps: # ethtool -c eth1 Coalesce parameters for eth1: Adaptive RX: off TX: off # ethtool -C eth1 adaptive-rx on # cat /etc/os-release NAME="Ubuntu" VERSION="16.04 (Xenial Xerus)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.04" VERSION_ID="16.04"

[Bug 1557950] Re: mlx5_core kernel trace after "ethtool -C eth1 adaptive-rx on" flow

** Patch added: "0002-net-mlx5e-Don-t-modify-CQ-before-it-was-created.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1557950/+attachment/4600895/+files/0002-net-mlx5e-Don-t-modify-CQ-before-it-was-created.patch -- You received this bug notification because you are a member of

[Bug 1557950] Re: mlx5_core kernel trace after "ethtool -C eth1 adaptive-rx on" flow

** Patch added: "0001-net-mlx5e-Don-t-try-to-modify-CQ-moderation-if-it-is.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1557950/+attachment/4600894/+files/0001-net-mlx5e-Don-t-try-to-modify-CQ-moderation-if-it-is.patch -- You received this bug notification because you are a

[Bug 1529815] Re: InfiniBand DHCP flow with PRA and DHCP relay not working

The DHCP Relay issue still has not been resolved. The issue was DHCP Offer packets that being sent from the DHCP server are not reaching the client. Setup: DHCP Client: IB SideUbuntu OS with ConnectX3 FW ver 2.35.5000, Mellanox OFED 3.2-1.0.1 DHCP Server: ETH Side Win2012

[Bug 1470167] Re: mstflint doesn't support Mellanox ConnectX-4 HCAs

Thank you, The mstflint4 work properly on Trusty, verified with ConnectX4 device. Please create the same to wily and vivid. Thanks, Talat -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1470167 Title

  1   2   >