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

[Talat Batheesh]

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 notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851446

Title:
  Backport MPLS patches from 5.3 to 4.15

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851446/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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:
  [cosmic] ipoib ping with large message size failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801574/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801574/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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.
https://bugs.launchpad.net/bugs/1801574

Title:
  [cosmic] ipoib ping with large message size failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801574/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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 check with the canonical kernel team why they revert that 
commit? 
To reproduce the bug, please use ConnectX-3 devices with ipoib connection with 
2044 MTU (default) and run command [2].
Is there open Launchpad on it?
 
[1]
commit 77a24c313d21e3765b04d90521e9228a9bb6e332
Author: Tyler Hicks 
Date:   Fri Aug 3 21:53:15 2018 +
 
Revert "net: increase fragment memory usage limits"
 
This reverts commit c2a936600f78aea00d3312ea4b66a79a4619f9b4. It
made denial of service attacks on the IP fragment handling easier to
carry out.
 
CVE-2018-5391
 
Signed-off-by: Tyler Hicks 
Signed-off-by: Stefan Bader 
 
[2]
ping 13.194.22.1 -I 13.194.23.1 -s 65507

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Incomplete


** Tags: cosmic

** Summary changed:

- [bionic] ipoib ping with large message size failed
+ [cosmic] ipoib ping with large message size failed

-- 
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:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801574/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799049/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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

Title:
  [bionic]mlx5: reading SW stats through ifstat cause kernel crash

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799049/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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
- Ubuntu 18.04 on Intel Skylake server
- gcc (Ubuntu 7.3.0-16ubuntu3) 7.3.0
- Testpmd crashes when it starts to forward traffic. Easy to reproduce.
- Only happens on the Skylake server.
- DPDK 18.05 and later don't have such issue. git-bisect gives no clue.

This is because I enabled MEMPOOL_DEBUG and MLX5_DEBUG. As mempool/rte_memcpy is
inlined function, it should be affected. Now I can see the crash regardlessly -
18.02, 18.05 and 18.08.

[2] Failure point

The attached patch gives an insight of why it crashes. The following is the
result of the patch and the GDB commands.

In summary, rte_memcpy() doesn't work as expected. In __mempool_generic_put(),
there's rte_memcpy() to move the array of objects to the lcore cache. If I run
memcmp() right after rte_memcpy(dst, src, n), data in dst differs from data in
src. And it looks like some of data got shifted by a few bytes as you can see
below.

[GDB command]
$dst = 0x74e09ea8
$src = 0x7fffce3fb970
$n = 256
x/32gx 0x74e09ea8
x/32gx 0x7fffce3fb970
testpmd: /home/mlnxtest/dpdk/build/include/rte_mempool.h:1140: 
__mempool_generic_put: Assertion `0' failed.

Thread 4 "lcore-slave-1" received signal SIGABRT, Aborted.
[Switching to Thread 0x7fffce3ff700 (LWP 69913)]
(gdb) x/32gx 0x74e09ea8
0x74e09ea8: 0x7fffaac38ec0  0x7fffaac38500
0x74e09eb8: 0x7fffaac37b40  0x7fffaac37180
0x74e09ec8: 0x85007fffaac3  0x7b407fffaac3
0x74e09ed8: 0x7fffaac35440  0x7fffaac34a80
0x74e09ee8: 0xaac385007fff  0xaac37b407fff
0x74e09ef8: 0x7fffaac32d40  0x7fffaac32380
0x74e09f08: 0x7fffaac38500  0x7fffaac37b40
0x74e09f18: 0x7fffaac30640  0x7fffaac2fc80
0x74e09f28: 0x7fffaac2f2c0  0x7fffaac2e900
0x74e09f38: 0x7fffaac2df40  0x7fffaac2d580
0x74e09f48: 0x7fffaac2cbc0  0x7fffaac2c200
0x74e09f58: 0x7fffaac2b840  0x7fffaac2ae80
0x74e09f68: 0x7fffaac2a4c0  0x7fffaac29b00
0x74e09f78: 0x7fffaac29140  0x7fffaac28780
0x74e09f88: 0x7fffaac27dc0  0x7fffaac27400
0x74e09f98: 0x7fffaac26a40  0x7fffaac26080
(gdb) x/32gx 0x7fffce3fb970
0x7fffce3fb970: 0x7fffaac38ec0  0x7fffaac38500
0x7fffce3fb980: 0x7fffaac37b40  0x7fffaac37180
0x7fffce3fb990: 0x7fffaac367c0  0x7fffaac35e00
0x7fffce3fb9a0: 0x7fffaac35440  0x7fffaac34a80
0x7fffce3fb9b0: 0x7fffaac340c0  0x7fffaac33700
0x7fffce3fb9c0: 0x7fffaac32d40  0x7fffaac32380
0x7fffce3fb9d0: 0x7fffaac319c0  0x7fffaac31000
0x7fffce3fb9e0: 0x7fffaac30640  0x7fffaac2fc80
0x7fffce3fb9f0: 0x7fffaac2f2c0  0x7fffaac2e900
0x7fffce3fba00: 0x7fffaac2df40  0x7fffaac2d580
0x7fffce3fba10: 0x7fffaac2cbc0  0x7fffaac2c200
0x7fffce3fba20: 0x7fffaac2b840  0x7fffaac2ae80
0x7fffce3fba30: 0x7fffaac2a4c0  0x7fffaac29b00
0x7fffce3fba40: 0x7fffaac29140  0x7fffaac28780
0x7fffce3fba50: 0x7fffaac27dc0  0x7fffaac27400
0x7fffce3fba60: 0x7fffaac26a40  0x7fffaac26080


AFAIK, AVX512F support is disabled by default in DPDK as it is still
experimental (CONFIG_RTE_ENABLE_AVX512=n). But with gcc optimization, AVX2
version of rte_memcpy() seems to be optimized with 512b instructions. If I
disable it by adding EXTRA_CFLAGS="-mno-avx512f", then it works fine and doesn't
crash.

Do you have any idea regarding this issue or are you already aware of
it?


Thanks,
Yongseok


$ git diff
diff --git a/config/common_base b/config/common_base
index ad03cf433..f512b5a88 100644
--- a/config/common_base
+++ b/config/common_base
@@ -275,8 +275,8 @@ CONFIG_RTE_LIBRTE_MLX4_TX_MP_CACHE=8
 #
 # Compile burst-oriented Mellanox ConnectX-4 & ConnectX-5 (MLX5) PMD
 #
-CONFIG_RTE_LIBRTE_MLX5_PMD=n
-CONFIG_RTE_LIBRTE_MLX5_DEBUG=n
+CONFIG_RTE_LIBRTE_MLX5_PMD=y
+CONFIG_RTE_LIBRTE_MLX5_DEBUG=y
 CONFIG_RTE_LIBRTE_MLX5_DLOPEN_DEPS=n
 CONFIG_RTE_LIBRTE_MLX5_TX_MP_CACHE=8

@@ -597,7 +597,7 @@ CONFIG_RTE_RING_USE_C11_MEM_MODEL=n
 #
 CONFIG_RTE_LIBRTE_MEMPOOL=y
 CONFIG_RTE_MEMPOOL_CACHE_MAX_SIZE=512
-CONFIG_RTE_LIBRTE_MEMPOOL_DEBUG=n
+CONFIG_RTE_LIBRTE_MEMPOOL_DEBUG=y

 #
 # Compile Mempool drivers
diff --git a/lib/librte_mempool/rte_mempool.h 

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

[Talat Batheesh]

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 cpu_hit


Actual results:
System will crash

Expected results:
No system crash

Additional info:
The reason for the crash is insufficient check on the helper that determines if 
a netdev is vf rep.

will crash:
$ ifstat -x cpu_hit 

will not crash:
$ ifstat -x cpu_hit $VF_REP 
$ ifstat -x cpu_hit $UPLINK_REP

We already have a fix for this issue, and it is accepted upstream.
https://patchwork.ozlabs.org/patch/935193/

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799049/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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, 
SR-IOV,Passthrough, etc..) in hypervisor.
This should impact on user that installed libibverbs1/MLNX_OFED and uses 
virtualization.

Could you please assist with knowing the reason of the dependency between 
qemu-system-x86 and libibverbs ? 
In the older releases we didn't see this issue


[1]
  ibverbs-providers libibverbs1 librados2 librbd1 librdmacm1 qemu 
qemu-block-extra qemu-system qemu-system-arm qemu-system-common 
qemu-system-mips qemu-system-misc qemu-system-ppc
  qemu-system-s390x qemu-system-sparc qemu-system-x86 qemu-utils

[2]
Example:

root@reg-l-vrt-120:~# apt-get remove libibverbs1  
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages were automatically installed and are no longer required:
  at cpu-checker cryptsetup cryptsetup-bin db-util db5.3-util dctrl-tools 
debootstrap devscripts dput extlinux fonts-droid-fallback fonts-noto-mono 
ghostscript hfsplus icoutils
  ipxe-qemu ipxe-qemu-256k-compat-efi-roms kpartx ldmtool libafflib0v5 
libapt-pkg-perl libasound2 libasound2-data libb-hooks-endofscope-perl 
libb-hooks-op-check-perl libbfio1
  libbluetooth3 libbrlapi0.6 libclass-method-modifiers-perl 
libclass-xsaccessor-perl libclone-perl libconfig9 libcupsfilters1 libcupsimage2 
libdata-optlist-perl libdate-manip-perl
  libdevel-callchecker-perl libdevel-globaldestruction-perl libdistro-info-perl 
libdynaloader-functions-perl libemail-valid-perl libewf2 libexporter-tiny-perl 
libfdt1
  libfile-basedir-perl libfile-chdir-perl libfile-homedir-perl 
libfile-which-perl libgetopt-long-descriptive-perl libgit-wrapper-perl libgs9 
libgs9-common libhfsp0 libhivex0
  libijs-0.35 libimport-into-perl libintl-perl libintl-xs-perl libio-pty-perl 
libio-stringy-perl libipc-run-perl libipc-system-simple-perl libiscsi7 
libjbig2dec0 libldm-1.0-0
  liblist-compare-perl liblist-moreutils-perl libmodule-implementation-perl 
libmodule-runtime-perl libmoo-perl libnamespace-clean-perl libnet-dns-perl 
libnet-domain-tld-perl
  libnet-ip-perl libnetpbm10 libnumber-compare-perl libnumber-range-perl 
libpackage-stash-perl libpackage-stash-xs-perl libpaper-utils libpaper1 
libparams-classify-perl
  libparams-util-perl libparams-validate-perl libpath-iterator-rule-perl 
libpath-tiny-perl libperlio-gzip-perl libpod-constants-perl 
libregexp-pattern-license-perl
  librole-tiny-perl libsdl1.2debian libsort-key-perl libsort-versions-perl 
libspice-server1 libstrictures-perl libstring-copyright-perl 
libstring-escape-perl
  libstring-shellquote-perl libsub-exporter-perl 
libsub-exporter-progressive-perl libsub-identify-perl libsub-install-perl 
libsub-quote-perl libsys-virt-perl libtext-glob-perl
  libtext-levenshtein-perl libtsk13 libunicode-utf8-perl libvariable-magic-perl 
libwin-hivex-perl libxml-xpath-perl libyaml-libyaml-perl licensecheck lintian 
lsscsi lzop msr-tools
  mtools netpbm poppler-data python-argcomplete python-cheetah python3-debian 
python3-gpg python3-magic python3-unidiff python3-xdg qemu-slof scrub seabios 
sgabios sharutils
  sleuthkit squashfs-tools supermin syslinux syslinux-common t1utils unzip 
zerofree
Use 'apt autoremove' to remove them.
The following packages will be REMOVED:
  ibverbs-providers libibverbs1 librados2 librbd1 librdmacm1 qemu 
qemu-block-extra qemu-system qemu-system-arm qemu-system-common 
qemu-system-mips qemu-system-misc qemu-system-ppc
  qemu-system-s390x qemu-system-sparc qemu-system-x86 qemu-utils
0 upgraded, 0 newly installed, 17 to remove and 0 not upgraded.
After this operation, 266 MB disk space will be freed.
Do you want to continue? [Y/n] n
To see dependencies:


[3]


root@reg-l-vrt-189:~# apt-cache depends qemu-system-x86
qemu-system-x86
  Depends: libaio1
  Depends: libasound2
  Depends: libbluetooth3
  Depends: libbrlapi0.6
  Depends: libc6
  Depends: libcacard0
  Depends: libfdt1
  Depends: libgcc1
  Depends: libglib2.0-0
  Depends: libgnutls30
  Depends: libibverbs1
  Depends: libjpeg8
  Depends: libncursesw5
  Depends: libnettle6
  Depends: libnuma1
  Depends: libpixman-1-0
  Depends: libpng16-16
  Depends: libpulse0
  Depends: librdmacm1
  Depends: libsasl2-2
  Depends: libsdl1.2debian
  Depends: libseccomp2
  Depends: libspice-server1
  Depends: libtinfo5
  Depends: libusb-1.0-0
  Depends: libusbredirparser1
  Depends: libx11-6
  Depends: libxen-4.9
  Depends: libxenstore3.0
  Depends: zlib1g
  Depends: qemu-system-common
qemu-system-common:i386
  Depends: seabios
  Depends: ipxe-qemu
  Depends: ipxe-qemu-256k-compat-efi-roms
  Recommends: qemu-utils
qemu-utils:i386
  Recommends: cpu-checker
  Suggests: samba
  Suggests: vde2
  Suggests: qemu-block-extra
  Suggests: kmod
kmod:i386
  

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

[Talat Batheesh]

** 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 when nvmet_rdma
  module is loaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764982/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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 is loaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764982/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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 about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1774132/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

** 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

Title:
  [Bionic]udev stop notifying when network interface added

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1774132/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

** 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

Title:
  [Bionic]udev stop notifying when network interface added

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1774132/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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 interface service 
doesn't start.

More details:

We see this issue when using Mellanox OFED package.
Mellanox OFED add a service per network device and add udev rule to start this 
service when the interface added.
After driver restart ("/etc/init.d/openibd restart") the network devices 
doesn't loaded, since udev doesn't notify.

The system should run from udev rules, since once the driver creates an
interface, there should be a udev event saying a new interface is added,
then this script will be ran by udev (the OS).

" /bin/systemctl --no-block start mlnx_interface_mgr@ib0.service "

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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 about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1774132/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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-
mode=rxonly

testpmd> port stop all
Then add the following rules:

flow create 0 ingress pattern eth dst spec ec:0d:9a:46:a0:04  dst mask 
FF:FF:FF:FF:FF:FF  src spec 00:16:3e:3f:74:39  src prefix 48  / vlan vid spec 
1578  vid mask 0xff0  / ipv6 src spec ::7eb1  src mask 
:::::::  dst spec ::7eb1  dst mask 
:::::::  proto is 47  tc spec 0  tc mask 0x0  / 
end actions rss queues  0 end  / end
flow create 0 ingress pattern eth dst spec ec:0d:9a:46:a0:04  dst mask 
FF:FF:FF:FF:FF:00  src spec 00:16:3e:6b:52:3e  src prefix 0  / vlan vid spec 
1062  vid prefix 8  / ipv6 dst spec ::d739  dst prefix 128  proto spec 47  
proto prefix 0  flow is 0  / end actions rss queues  0 end  / end
flow create 0 ingress pattern eth src spec 00:16:3e:75:1a:e3  src mask 
FF:FF:FF:FF:FF:00  / ipv4 dst spec 234.191.135.109  dst mask 0.0.0.0  proto 
spec 17  proto mask 0x0  tos spec 36  tos prefix 8  / end actions rss queues  0 
end  / mark id 36 / end
flow create 0 ingress pattern end actions rss queues  0 end  / end
flow create 0 ingress pattern eth dst spec ec:0d:9a:46:a0:04  dst prefix 32  
src is 00:16:3e:61:7f:dd  / ipv4 src spec 195.14.171.117  src mask 
255.255.255.255  proto spec 17  proto mask 0x0  / udp src spec 49934  src mask 
0x  / vxlan vni spec 8497260  vni mask 0xff  / end actions rss queues  
0 end  / mark id 62 / end
testpmd> port start all
Then restart the ports:
testpmd> port stop all
testpmd> port start all

testpmd>start

Then send the following packet via scapy:

packet = Ether(src='00:16:3e:3f:74:39', dst='ec:0d:9a:46:a0:04', 
type=33024)/Dot1Q(vlan=1573, type=34525, id=0, prio=0)/IPv6(nh=47, 
src='::7eb1', dst='9e8e:6edc:62cf:7058:b032:7fe2:4001:a95b', version=6, hlim=1, 
plen=1442, fl=0, tc=1
)/GRE(routing_present=1, chksum_present=1, version=6, proto=17990, 
offset=17990, strict_route_source=0, seqnum_present=0, key_present=0, 
recursion_control=6, flags=8, key=None, chksum=55897, seqence_number=None)
packet.add_payload('F' * (1496 - len(packet) - 4 ))
sendp(packet, iface = 'ens6', count = 1)

Real result testpmd didn't received any traffic
More details:
Setups:dragon41-cx5100g
TG: dragon40-cx5100g
OS:Ubuntu 18.04
OFED:N/A
FW:fw 16.22.4020


below is patch that fix this issue.

http://dpdk.org/ml/archives/stable/2018-April/005898.html

** Affects: dpdk (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770964

Title:
  [Bionic][RSS][ConnectX5]:testpmd stop receiving the packets after
  restarting the ports

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1770964/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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 when nvmet_rdma
  module is loaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764982/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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 dev bond0
 # ip link set bond0 up
 # echo +eth5 > /sys/class/net/bond0/bonding/slaves
 # echo +eth4 > /sys/class/net/bond0/bonding/slaves
 # echo -eth4 > /sys/class/net/bond0/bonding/slaves
 # echo -eth5 > /sys/class/net/bond0/bonding/slaves
 # echo -bond0 > /sys/class/net/bonding_masters


dmesg:

kernel: [78348.225556] bond0 (unregistering): Released all slaves
kernel: [78358.339631] unregister_netdevice: waiting for bond0 to become free. 
Usage count = 2
kernel: [78368.419621] unregister_netdevice: waiting for bond0 to become free. 
Usage count = 2
kernel: [78378.499615] unregister_netdevice: waiting for bond0 to become free. 
Usage count = 2
kernel: [78388.579625] unregister_netdevice: waiting for bond0 to become free. 
Usage count = 2
kernel: [78398.659613] unregister_netdevice: waiting for bond0 to become free. 
Usage count = 2
kernel: [78408.739655] unregister_netdevice: waiting for bond0 to become free. 
Usage count = 2
kernel: [78418.819634] unregister_netdevice: waiting for bond0 to become free. 
Usage count = 2
kernel: [78428.899642] unregister_netdevice: waiting for bond0 to become free. 
Usage count = 2
kernel: [78438.979614] unregister_netdevice: waiting for bond0 to become free. 
Usage count = 2
kernel: [78449.059619] unregister_netdevice: waiting for bond0 to become free. 
Usage count = 2
kernel: [78459.139626] unregister_netdevice: waiting for bond0 to become free. 
Usage count = 2
kernel: [78469.219623] unregister_netdevice: waiting for bond0 to become free. 
Usage count = 2
kernel: [78479.299619] unregister_netdevice: waiting for bond0 to become free. 
Usage count = 2
kernel: [78489.379620] unregister_netdevice: waiting for bond0 to become free. 
Usage count = 2
kernel: [78499.459623] unregister_netdevice: waiting for bond0 to become free. 
Usage count = 2
kernel: [78509.539631] unregister_netdevice: waiting for bond0 to become free. 
Usage count = 2
kernel: [78519.619629] unregister_netdevice: waiting for bond0 to become free. 
Usage count = 2


The following upstream commits that fix this issue


commit a3dd7d0022c347207ae931c753a6dc3e6e8fcbc1
Author: Max Gurtovoy 
Date:   Wed Feb 28 13:12:38 2018 +0200

nvmet-rdma: Don't flush system_wq by default during remove_one

The .remove_one function is called for any ib_device removal.
In case the removed device has no reference in our driver, there
is no need to flush the system work queue.

Reviewed-by: Israel Rukshin 
Signed-off-by: Max Gurtovoy 
Reviewed-by: Sagi Grimberg 
Signed-off-by: Keith Busch 
Signed-off-by: Jens Axboe 

diff --git a/drivers/nvme/target/rdma.c b/drivers/nvme/target/rdma.c
index aa8068f..a59263d 100644
--- a/drivers/nvme/target/rdma.c
+++ b/drivers/nvme/target/rdma.c
@@ -1469,8 +1469,25 @@ static struct nvmet_fabrics_ops nvmet_rdma_ops = {
 static void nvmet_rdma_remove_one(struct ib_device *ib_device, void 
*client_data)
 {
struct nvmet_rdma_queue *queue, *tmp;
+ struct nvmet_rdma_device *ndev;
+ bool found = false;
+
+ mutex_lock(_list_mutex);
+ list_for_each_entry(ndev, _list, entry) {
+ if (ndev->device == ib_device) {
+ found = true;
+ break;
+ }
+ }
+ mutex_unlock(_list_mutex);
+
+ if (!found)
+ return;

-   /* Device is being removed, delete all queues using this device */
+ /*
+  * IB Device that is used by nvmet controllers is being removed,
+  * delete all queues using this device.
+  */
mutex_lock(_rdma_queue_mutex);
list_for_each_entry_safe(queue, tmp, _rdma_queue_list,
 queue_list) {


commit 9bad0404ecd7594265cef04e176adeaa4ffbca4a
Author: Max Gurtovoy 
Date:   Wed Feb 28 13:12:39 2018 +0200

nvme-rdma: Don't flush delete_wq by default during remove_one

The .remove_one function is called for any ib_device removal.
In case the removed device has no reference in our driver, there
is no need to flush the work queue.

Reviewed-by: Israel Rukshin 
Signed-off-by: Max Gurtovoy 
Reviewed-by: Sagi Grimberg 
Signed-off-by: Keith Busch 
Signed-off-by: Jens Axboe 

diff --git a/drivers/nvme/host/rdma.c b/drivers/nvme/host/rdma.c
index f5f460b..250b277 100644
--- a/drivers/nvme/host/rdma.c
+++ b/drivers/nvme/host/rdma.c
@@ -2024,6 +2024,20 @@ static struct nvmf_transport_ops nvme_rdma_transport = {
 static void nvme_rdma_remove_one(struct ib_device *ib_device, void 
*client_data)
 {
struct 

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

[Talat Batheesh]

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  
rx_cqe_compress: off 

After applying the patch

# ethtool --show-priv-flags enp6s0f0 
Private flags for enp6s0f0:  
rx_cqe_moder   : on  
tx_cqe_moder   : off 
rx_cqe_compress: off

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763325

Title:
  [bionic] ConnectX5 Large message size throughput degradation in TCP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763325/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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.


There is an upstream commit that fix this issue, I will backport it and send it 
to the kernel-t...@lists.ubuntu.com


commit 48bfc39791b8b4a25f165e711f18b9c1617cefbc 

 
Author: Tal Gilboa  

 
Date:   Fri Mar 30 15:50:08 2018 -0700  

 

net/mlx5e: Set EQE based as default TX interrupt moderation mode

The default TX moderation mode was mistakenly set to CQE based. The
intention was to add a control ability in order to improve some specific
use-cases. In general, we prefer to use EQE based moderation as it gives
much better numbers for the common cases.

CQE based causes a degradation in the common case since it resets the
moderation timer on CQE generation. This causes an issue when TSO is
well utilized (large TSO sessions). The timer is set to 16us so traffic
of ~64KB TSO sessions per second would mean timer reset (CQE per TSO
session -> long time between CQEs). In this case we quickly reach the
tcp_limit_output_bytes (256KB by default) and cause a halt in TX traffic.

By setting EQE based moderation we make sure timer would expire after
16us regardless of the packet rate.
This fixes an up to 40% packet rate and up to 23% bandwidth degradtions.

Fixes: 0088cbbc4b66 ("net/mlx5e: Enable CQE based moderation on TX CQ")
Signed-off-by: Tal Gilboa 
Signed-off-by: Saeed Mahameed 
Signed-off-by: David S. Miller 

diff --git a/drivers/net/ethernet/mellanox/mlx5/core/en_main.c 
b/drivers/net/ethernet/mellanox/mlx5/core/en_main.c
index c71f4f10283b..0aab3afc6885 100644
--- a/drivers/net/ethernet/mellanox/mlx5/core/en_main.c
+++ b/drivers/net/ethernet/mellanox/mlx5/core/en_main.c
@@ -4137,7 +4137,7 @@ void mlx5e_build_nic_params(struct mlx5_core_dev *mdev,
struct mlx5e_params *params,
u16 max_channels, u16 mtu)
 {
-   u8 cq_period_mode = 0;
+ u8 rx_cq_period_mode;

params->sw_mtu = mtu;
params->hard_mtu = MLX5E_ETH_HARD_MTU;
@@ -4173,12 +4173,12 @@ void mlx5e_build_nic_params(struct mlx5_core_dev *mdev,
params->lro_timeout = mlx5e_choose_lro_timeout(mdev, 
MLX5E_DEFAULT_LRO_TIMEOUT);

/* CQ moderation params */
-   cq_period_mode = MLX5_CAP_GEN(mdev, cq_period_start_from_cqe) ?
+ rx_cq_period_mode = MLX5_CAP_GEN(mdev, cq_period_start_from_cqe) ?
MLX5_CQ_PERIOD_MODE_START_FROM_CQE :
MLX5_CQ_PERIOD_MODE_START_FROM_EQE;
params->rx_dim_enabled = MLX5_CAP_GEN(mdev, cq_moderation);
-   mlx5e_set_rx_cq_mode_params(params, cq_period_mode);
-   mlx5e_set_tx_cq_mode_params(params, cq_period_mode);
+ mlx5e_set_rx_cq_mode_params(params, rx_cq_period_mode);
+ mlx5e_set_tx_cq_mode_params(params, MLX5_CQ_PERIOD_MODE_START_FROM_EQE);

/* TX inline */
params->tx_min_inline_mode = mlx5e_params_calculate_tx_min_inline(mdev);

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763325

Title:
  [bionic] ConnectX5 Large message size throughput degradation in TCP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763325/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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 * 100 cannot be represented in type 'int'
[12885.304001] CPU: 2 PID: 19630 Comm: sock_stream_tes Tainted: G   OE  
  4.15.0-rc8-for-upstream-dbg-2018-01-25_19-31-23-61 #1
[12885.311856] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Ubuntu-1.8.2-1ubuntu2 04/01/2014
[12885.316091] Call Trace:
[12885.320234]  
[12885.324366]  dump_stack+0xd1/0x159
[12885.328586]  ? dma_virt_map_sg+0x147/0x147
[12885.332804]  ? val_to_string.constprop.4+0x88/0xd1
[12885.337055]  ubsan_epilogue+0x9/0x49
[12885.341345]  handle_overflow+0x15e/0x189
[12885.345636]  ? __ubsan_handle_negate_overflow+0x108/0x108
[12885.349891]  ? kvm_clock_read+0x1f/0x30
[12885.354230]  ? ktime_get+0x18d/0x280
[12885.358654]  ? getrawmonotonic64+0x320/0x320
[12885.363116]  ? mark_lock+0x1cf/0xc50
[12885.367624]  ? inet_recvmsg+0x121/0x4a0
[12885.372114]  mlx5e_napi_poll+0x1199/0x15c0 [mlx5_core]
[12885.376774]  ? mlx5e_rx_dim_work+0x160/0x160 [mlx5_core]
[12885.381406]  ? print_irqtrace_events+0x120/0x120
[12885.385907]  ? mark_held_locks+0x93/0x100
[12885.392099]  ? print_irqtrace_events+0x120/0x120
[12885.396589]  ? trace_hardirqs_on_caller+0x206/0x390
[12885.401278]  ? kasan_slab_free+0x87/0xc0
[12885.406000]  ? pvclock_clocksource_read+0x146/0x280
[12885.410608]  ? mark_held_locks+0x71/0x100
[12885.415251]  net_rx_action+0x58c/0x10a0
[12885.419873]  ? napi_complete_done+0x3d0/0x3d0
[12885.424385]  ? check_chain_key+0x150/0x260
[12885.428784]  ? debug_check_no_locks_freed+0x200/0x200
[12885.433041]  ? match_held_lock+0x8a/0x4f0
[12885.437215]  ? match_held_lock+0x8a/0x4f0
[12885.441249]  ? lock_downgrade+0x3e0/0x3e0
[12885.445151]  ? do_raw_spin_unlock+0x14d/0x230
[12885.448970]  ? save_trace+0x1f0/0x1f0
[12885.452664]  ? save_trace+0x1f0/0x1f0
[12885.456224]  ? match_held_lock+0xa2/0x4f0
[12885.459668]  ? pvclock_clocksource_read+0x146/0x280
[12885.463085]  ? save_trace+0x1f0/0x1f0
[12885.466361]  ? preempt_count_sub+0x14/0xd0
[12885.469566]  ? __lock_is_held+0x5d/0x110
[12885.472665]  ? preempt_count_sub+0x14/0xd0
[12885.475653]  ? __lock_is_held+0x5d/0x110
[12885.478529]  ? mark_lock+0x1cf/0xc50
[12885.481276]  ? match_held_lock+0xa2/0x4f0
[12885.483984]  ? print_irqtrace_events+0x120/0x120
[12885.486679]  ? save_trace+0x1f0/0x1f0
[12885.490891]  ? irq_exit+0x150/0x150
[12885.493454]  ? __napi_schedule+0x1ae/0x220
[12885.495936]  ? netdev_master_upper_dev_link+0x20/0x20
[12885.498402]  ? check_chain_key+0x150/0x260
[12885.500774]  ? __tasklet_schedule+0x22/0xf0
[12885.503086]  ? match_held_lock+0xa2/0x4f0
[12885.505431]  ? mlx5_eq_int+0x821/0xb50 [mlx5_core]
[12885.507775]  ? save_trace+0x1f0/0x1f0
[12885.510082]  ? pvclock_clocksource_read+0x146/0x280
[12885.512416]  ? pvclock_read_flags+0x80/0x80
[12885.514705]  ? save_trace+0x1f0/0x1f0
[12885.516995]  ? __handle_irq_event_percpu+0x1b0/0x800
[12885.519305]  ? __lock_is_held+0x5d/0x110
[12885.521630]  __do_softirq+0x248/0xba9
[12885.523913]  ? __irqentry_text_end+0x1f8a70/0x1f8a70
[12885.526234]  ? pvclock_clocksource_read+0x146/0x280
[12885.528563]  ? pvclock_read_flags+0x80/0x80
[12885.530843]  ? do_raw_spin_trylock+0x120/0x120
[12885.533178]  ? kvm_clock_read+0x1f/0x30
[12885.535432]  ? kvm_sched_clock_read+0x5/0x10
[12885.537702]  ? sched_clock_cpu+0x14/0x1f0
[12885.539968]  irq_exit+0xf4/0x150
[12885.542186]  do_IRQ+0xe8/0x1e0
[12885.544390]  common_interrupt+0xa2/0xa2
[12885.546607]  
There is int overflow in:
include/linux/net_dim.h 
#define IS_SIGNIFICANT_DIFF(val, ref) \
(((100 * abs((val) - (ref))) / (ref)) > 10) /* more than 10% difference */


The include/linux/net_dim.h library in new in kernel 4.16, in 4.15 kernel this 
code was in drivers/net/ethernet/mellanox/mlx5/core/en_rx_am.c 

The upstream fix that fix this issue is 
commit f97c3dc3c0e8d23a5c4357d182afeef4c67f5c33
Author: Tal Gilboa 
Date:   Thu Mar 29 13:53:52 2018 +0300

net/dim: Fix int overflow

When calculating difference between samples, the values
are multiplied by 100. Large values may cause int overflow
when multiplied (usually on first iteration).
Fixed by forcing 100 to be of type unsigned long.

Fixes: 4c4dbb4a7363 ("net/mlx5e: Move dynamic interrupt coalescing code to 
include/linux")
Signed-off-by: Tal Gilboa 
Reviewed-by: Andy Gospodarek 
Signed-off-by: David S. Miller 

diff --git a/include/linux/net_dim.h b/include/linux/net_dim.h
index bebeaad..29ed8fd 100644
--- a/include/linux/net_dim.h
+++ b/include/linux/net_dim.h
@@ -231,7 +231,7 @@ static inline void net_dim_exit_parking(struct net_dim *dim)
 }

 #define IS_SIGNIFICANT_DIFF(val, ref) \
-   (((100 * abs((val) - (ref))) / 

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

[Talat Batheesh]

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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758662/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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 go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758662/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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


There is a upstream commit that fix the issue, please add it to bionic 

commit a42b63c1ac1986f17f71bc91a6b0aaa14d4dae71  
Author: Moni Shoua   
Date:   Thu Dec 28 16:26:11 2017 +0200   

net/mlx4_en: Change default QoS settings

Change the default mapping between TC and TCG as follows:
 
Prio | TC/TCG
 |  from to  
 |(set by FW)  (set by SW)   
-+---
0|  0/0  0/7 
1|  1/0  0/6 
2|  2/0  0/5 
3|  3/0  0/4 
4|  4/0  0/3 
5|  5/0  0/2 
6|  6/0  0/1 
7|  7/0  0/0 
 
These new settings cause that a pause frame for any prio stops
traffic for all prios.
  
Fixes: 564c274c3df0 ("net/mlx4_en: DCB QoS support")  
Signed-off-by: Moni Shoua 
Signed-off-by: Maor Gottlieb  
Signed-off-by: Tariq Toukan  
Signed-off-by: David S. Miller   

diff --git a/drivers/net/ethernet/mellanox/mlx4/en_dcb_nl.c 
b/drivers/net/ethernet/mellanox/mlx4/en_dcb_nl.c
index 5f41dc9..1a0c3bf8 100644  

--- a/drivers/net/ethernet/mellanox/mlx4/en_dcb_nl.c

+++ b/drivers/net/ethernet/mellanox/mlx4/en_dcb_nl.c
@@ -310,6 +310,7 @@ static int mlx4_en_ets_validate(struct mlx4_en_priv *priv, 
struct ieee_ets *ets)
}

switch (ets->tc_tsa[i]) {
+ case IEEE_8021QAZ_TSA_VENDOR:
case IEEE_8021QAZ_TSA_STRICT:
break;
case IEEE_8021QAZ_TSA_ETS:
@@ -347,6 +348,10 @@ static int mlx4_en_config_port_scheduler(struct 
mlx4_en_priv *priv,
/* higher TC means higher priority => lower pg */
for (i = IEEE_8021QAZ_MAX_TCS - 1; i >= 0; i--) {
switch (ets->tc_tsa[i]) {
+ case IEEE_8021QAZ_TSA_VENDOR:
+ pg[i] = MLX4_EN_TC_VENDOR;
+ tc_tx_bw[i] = MLX4_EN_BW_MAX;
+ break;
case IEEE_8021QAZ_TSA_STRICT:
pg[i] = num_strict++;
tc_tx_bw[i] = MLX4_EN_BW_MAX;
diff --git a/drivers/net/ethernet/mellanox/mlx4/en_netdev.c 
b/drivers/net/ethernet/mellanox/mlx4/en_netdev.c
index 99051a2..21bc17f 100644
--- a/drivers/net/ethernet/mellanox/mlx4/en_netdev.c
+++ b/drivers/net/ethernet/mellanox/mlx4/en_netdev.c
@@ -3336,6 +3336,13 @@ int mlx4_en_init_netdev(struct mlx4_en_dev *mdev, int 
port,
priv->msg_enable = MLX4_EN_MSG_LEVEL;
 #ifdef CONFIG_MLX4_EN_DCB
if (!mlx4_is_slave(priv->mdev->dev)) {
+ u8 prio;
+
+ for (prio = 0; prio < IEEE_8021QAZ_MAX_TCS; ++prio) {
+ priv->ets.prio_tc[prio] = prio;
+ priv->ets.tc_tsa[prio]  = IEEE_8021QAZ_TSA_VENDOR;
+ }
+
priv->dcbx_cap = DCB_CAP_DCBX_VER_CEE | DCB_CAP_DCBX_HOST |
DCB_CAP_DCBX_VER_IEEE;
priv->flags |= MLX4_EN_DCB_ENABLED;
diff --git a/drivers/net/ethernet/mellanox/mlx4/mlx4_en.h 
b/drivers/net/ethernet/mellanox/mlx4/mlx4_en.h
index 2b72677..7db3d0d 100644
--- a/drivers/net/ethernet/mellanox/mlx4/mlx4_en.h
+++ b/drivers/net/ethernet/mellanox/mlx4/mlx4_en.h
@@ -479,6 +479,7 @@ struct mlx4_en_frag_info {
 #define MLX4_EN_BW_MIN 1
 #define MLX4_EN_BW_MAX 100 /* Utilize 100% of the line */

+#define MLX4_EN_TC_VENDOR 0
 #define MLX4_EN_TC_ETS 7

 enum dcb_pfc_type {

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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 go to:

[Bug 1747170] Re: installer no ipv4 dhcp

[Talat Batheesh]

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://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1747170/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1719302/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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] 18.04 rdma-core as replacement for older ibverbs code

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rdma-core/+bug/1732892/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

Hi Seth,

Thank you for the review and for the detailed response.

The rdma-core was already accepted to debian and passed their acceptance 
process.
In addition rdma-core was already integrated into the other major linux distors 
(such as Fedora, RHEL, OpenSUSE, SLES, Debian ... ).

please note that rdma-core is a compilation of OLD libraries, most if
not all errors are OLD errors available in legacy libraries.

Reading the report, there are a lot FALSE positives. For example, all
resp.* warnings are false. resp is  initialize to be zero.

rdma-core is open source and you are very welcome 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 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 about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rdma-core/+bug/1732892/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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 about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rdma-core/+bug/1732892/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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*
#apt-get install radvd

2.Define DHCP and RADVD files:

#vim /etc/dhcp/dhcpd6.conf
authoritative;
default-lease-time 600;
max-lease-time 7200;
log-facility local7;
subnet6 ::/64 {
option dhcp6.name-servers ::;
range6 ::1 ::100;
}

#vim /etc/radvd.conf
interface enp5s0f0
{
AdvSendAdvert on;
MinRtrAdvInterval 3;
MaxRtrAdvInterval 10;
prefix ::/64 {
AdvOnLink on;
AdvAutonomous on;
AdvRouterAddr on;
};
};


3.
# sysctl net.ipv6.conf.ens3.forwarding
net.ipv6.conf.ens3.forwarding = 1

4.Create empty server data base file and bring up DHCP server:
#echo "" >  /tmp/dhcp6.lease
# dhcpd -6 -cf /etc/dhcp/dhcpd6.conf -lf /tmp/dhcpd6.leases enp5s0f0

5.Define client interface in /etc/network/interfaces file:
#vim  /etc/network/interfaces
auto enp6s0f0
iface enp6s0f0 inet6 dhcp

6.Start client and check the ip:
#ifdown 
#ifup
#ifconfig enp6s0f0

** Affects: isc-dhcp (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1715319

Title:
  [IPV6] DHCP client gets 128 subnet mask instead of any other that
  defined

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1715319/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1693503] Re: Remove mlx4.conf

[Talat Batheesh]

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, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1693503

Title:
  Remove mlx4.conf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1693503/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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, that resembles a
`SW Striding RQ`.
We allow the WQE to reuse its allocated page as much as it could,
until the page is fully consumed.  In each round, the WQE is capable
of receiving packet of maximal size (MTU). Yet, upon the reception of
a packet, the WQE knows the actual packet size, and consumes the exact
amount of memory needed to build a linear SKB. Then, it updates the
buffer pointer within the page accordingly, for the next round.

Feature is mutually exclusive with XDP (packet-per-page)
and LRO (session size is a power of two, needs unused page).

 Upstream acceptance Commits

accd58833237 net/mlx5e: Introduce RX Page-Reuse
bce2b2bf6682 net/mlx5e: Enhance RX SKB headroom logic
78aedd327982 net/mlx5e: Build SKB with exact frag_size

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Incomplete


** Tags: artful

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1701892

Title:
  [Artful] mlx5e-Introduce RX Page-Reuse

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1701892/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1693503] [NEW] Remove mlx4.conf

[Talat Batheesh]

Public bug reported:

Hi,

we are working on debianizing rdma-core package, it will contain a rdma
service that manage the mlx4.conf file, so the conf file
“/etc/modprobe.d/mlx4.conf” (that comes with “kmod” package) is not
needed anymore, and must be removed.

This conf file conflicts with “/lib/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 notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1693503

Title:
  Remove mlx4.conf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1693503/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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 changing ring size

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687877/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

Public bug reported:


The problem happens when changing the ring size of a mlx5_core interface that 
is part of a LACP bond.

[268312.721076] mlx5_core :42:00.1 enp66s0f1: mlx5e_update_carrier:143: 
Link up
[268312.721940] mlx5_core :42:00.1 enp66s0f1: speed changed to 0 for port 
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: Undecided
 Status: New

-- 
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 changing ring size

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687877/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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 nf_conntrack_ipv6 
nf_nat_ipv6 nf_defrag_ipv6 nfsv3 nfs fscache xt_CHECKSUM iptable_mangle 
ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat libcrc32c 
nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT 
nf_reject_ipv4 xt_tcpudp ebtable_filter ebtables ip6table_filter ip6_tables 
iptable_filter bridge stp llc binfmt_misc ipmi_ssif intel_rapl sb_edac 
edac_core x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm 
irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel 
aes_x86_64 crypto_simd glue_helper cryptd intel_cstate ipmi_si mei_me 
ipmi_devintf
[80921.652556]  dcdbas intel_rapl_perf mei shpchp lpc_ich ipmi_msghandler 
acpi_power_meter mac_hid nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables 
x_tables autofs4 mlx4_en mxm_wmi mlx5_core mlx4_core tg3 ahci megaraid_sas ptp 
libahci devlink pps_core fjes wmi
[80921.659813] CPU: 7 PID: 5743 Comm: kworker/u82:0 Not tainted 
4.10.0-19-generic #21-Ubuntu
[80921.662346] Hardware name: Dell Inc. PowerEdge R730/072T6D, BIOS 2.3.4 
11/08/2016
[80921.664686] Workqueue: events_freezable_power_ disk_events_workfn
[80921.666586] task: 96f69a285a00 task.stack: acc627394000
[80921.668437] RIP: 0010:kmem_cache_alloc+0x77/0x1a0
[80921.669902] RSP: 0018:acc6273978a8 EFLAGS: 00010086
[80921.671531] RAX:  RBX:  RCX: 00011c41
[80921.673758] RDX: 00011c40 RSI: 01080020 RDI: 0001c5c0
[80921.675985] RBP: acc6273978d8 R08: 96f6ff0dc5c0 R09: 0064
[80921.729078] R10: 96f6af006630 R11:  R12: 01080020
[80921.782687] R13: 957acd99 R14: 96eedf407980 R15: 96eedf407980
[80921.836867] FS:  () GS:96f6ff0c() 
knlGS:
[80921.944601] CS:  0010 DS:  ES:  CR0: 80050033
[80921.998508] CR2: 7fd1e8a75a08 CR3: 001062c09000 CR4: 003426e0
[80922.052471] DR0:  DR1:  DR2: 
[80922.105264] DR3:  DR6: fffe0ff0 DR7: 0400
[80922.156346] Call Trace:
[80922.205695]  ? kmem_cache_alloc+0xd3/0x1a0
[80922.254432]  alloc_iova+0x49/0x240
[80922.301753]  alloc_iova_fast+0x55/0x200
[80922.347916]  intel_alloc_iova+0xac/0xe0
[80922.392736]  intel_map_sg+0xc2/0x220
[80922.436095]  ? lock_timer_base+0x81/0xa0
[80922.478325]  ata_qc_issue+0x204/0x320

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682418

Title:
  [zesty] mlx5 OVS  vxlan ipv6 LNST test cause Oops

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682418/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678585/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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 this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678585/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

Public bug reported:

After running offload enabled LNST ipv6 vxlan ovs test 
(recipes/ovs_offload/1_virt_ovs_vxlan_ipv6.xml) with the setup that it creates 
multiple times till it crashes.
The test itself and other LNST tests pass, it's the shutdown phase that causes 
this.
There are different stack traces that usually relate to some kind of allocation 
(or ext4, inode), see one below.


scenario :
1. Install lnst tests 
   git clone https://github.com/jpirko/lnst.git && cd lnst && ./setup.py install
2. prepare OVS offload enable setup (2 machines) connected Back to Back
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] Oops:  [#1] SMP 

 
 kernel: [76406.419297] Modules linked in: act_mirred act_gact 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 nfsv3 nfs fscache xt_CHECKSUM 
iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat xt_conntrack 
ipt_REJECT nf_reject_ipv4 xt_tcpudp ebtable_filter ebtables ip6table_filter 
ip6_tables iptable_filter bridge stp llc openvswitch nf_conntrack_ipv6 
nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat 
nf_conntrack intel_rapl sb_edac edac_core x86_pkg_temp_thermal intel_powerclamp 
coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd 
ipmi_ssif intel_cstate ipmi_si input_leds joydev ipmi_devintf   

 
 kernel: [76406.981750]  mei_me dcdbas intel_rapl_perf shpchp mei 
ipmi_msghandler lpc_ich mac_hid acpi_power_meter configfs nfsd auth_rpcgss 
nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 btrfs raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear mlx4_en hid_generic tg3 mlx5_core usbhid 
mlx4_core ahci ptp mxm_wmi hid libahci megaraid_sas devlink pps_core fjes wmi   

   
 kernel: [76407.335099] CPU: 25 PID: 5253 Comm: ip Not tainted 
4.10.0-19-generic #21-Ubuntu
  
 kernel: [76407.446475] Hardware name: Dell Inc. PowerEdge R730/072T6D, BIOS 
2.3.4 11/08/2016

 kernel: [76407.558645] task: 9a2b76f89680 task.stack: bda6c76a8000 

 
 kernel: [76407.618666] RIP: 0010:rb_erase+0x194/0x350  

 
 kernel: [76407.676596] RSP: 0018:bda6c76ab4f0 EFLAGS: 00010046 

 
 kernel: [76407.735460] RAX: 9a2c2cc30bc0 RBX: 9a2c53372d18 RCX: 


 kernel: [76407.797100] RDX:  RSI: 9a2c53372d20 RDI: 
9a2c2cc30a40

 kernel: [76407.858831] RBP: bda6c76ab4f0 R08:  R09: 
00018040002e

 kernel: [76407.921323] R10: 9a2c2cc30b40 R11: 000f9e00 R12: 
9a2c2cc30a40

 kernel: [76407.984793] R13: 9a2c53372d18 R14: 0046 R15: 
9a2c5536b800

 kernel: [76408.048453] FS:  7f3d96082d80() GS:9a2c5f30() 
knlGS:  
   
 kernel: [76408.166912] CS:  0010 DS:  ES:  CR0: 80050033   

 
 

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

[Talat Batheesh]

Public bug reported:

Scenario:

$ifconfig
ens3: flags=4163  mtu 1500
inet 10.141.20.8  netmask 255.255.0.0  broadcast 10.141.255.255
inet6 fe80::250:56ff:fe8d:1408  prefixlen 64  scopeid 0x20
ether 00:50:56:8d:14:08  txqueuelen 1000  (Ethernet)
RX packets 152370  bytes 15937926 (15.9 MB)
RX errors 3  dropped 0  overruns 0  frame 3
TX packets 4092  bytes 470882 (470.8 KB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

ens8: flags=4163  mtu 1500
inet 11.141.20.8  netmask 255.255.0.0  broadcast 11.141.255.255
inet6 fe80::268a:7ff:fe1e:d572  prefixlen 64  scopeid 0x20
ether 24:8a:07:1e:d5:72  txqueuelen 1000  (Ethernet)
RX packets 0  bytes 0 (0.0 B)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 29  bytes 2280 (2.2 KB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73  mtu 65536
inet 127.0.0.1  netmask 255.0.0.0
inet6 ::1  prefixlen 128  scopeid 0x10
loop  txqueuelen 1000  (Local Loopback)
RX packets 200  bytes 16052 (16.0 KB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 200  bytes 16052 (16.0 KB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

$ping -c 10 -I ens8 11.141.20.8
PING 11.141.20.8 (11.141.20.8) from 11.141.20.8 ens8: 56(84) bytes of data.
^C
--- 11.141.20.8 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2050ms

$ping -c 10 -I ens3 10.141.20.8
PING 10.141.20.8 (10.141.20.8) from 10.141.20.8 ens3: 56(84) bytes of data.
^C
--- 10.141.20.8 ping statistics ---
10 packets transmitted, 0 received, 100% 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
  ens3: flags=4163  mtu 1500
- inet 10.141.20.8  netmask 255.255.0.0  broadcast 10.141.255.255
- inet6 fe80::250:56ff:fe8d:1408  prefixlen 64  scopeid 0x20
- ether 00:50:56:8d:14:08  txqueuelen 1000  (Ethernet)
- RX packets 152370  bytes 15937926 (15.9 MB)
- RX errors 3  dropped 0  overruns 0  frame 3
- TX packets 4092  bytes 470882 (470.8 KB)
- TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
+ inet 10.141.20.8  netmask 255.255.0.0  broadcast 10.141.255.255
+ inet6 fe80::250:56ff:fe8d:1408  prefixlen 64  scopeid 0x20
+ ether 00:50:56:8d:14:08  txqueuelen 1000  (Ethernet)
+ RX packets 152370  bytes 15937926 (15.9 MB)
+ RX errors 3  dropped 0  overruns 0  frame 3
+ TX packets 4092  bytes 470882 (470.8 KB)
+ TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
  
  ens8: flags=4163  mtu 1500
- inet 11.141.20.8  netmask 255.255.0.0  broadcast 11.141.255.255
- inet6 fe80::268a:7ff:fe1e:d572  prefixlen 64  scopeid 0x20
- ether 24:8a:07:1e:d5:72  txqueuelen 1000  (Ethernet)
- RX packets 0  bytes 0 (0.0 B)
- RX errors 0  dropped 0  overruns 0  frame 0
- TX packets 29  bytes 2280 (2.2 KB)
- TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
+ inet 11.141.20.8  netmask 255.255.0.0  broadcast 11.141.255.255
+ inet6 fe80::268a:7ff:fe1e:d572  prefixlen 64  scopeid 0x20
+ ether 24:8a:07:1e:d5:72  txqueuelen 1000  (Ethernet)
+ RX packets 0  bytes 0 (0.0 B)
+ RX errors 0  dropped 0  overruns 0  frame 0
+ TX packets 29  bytes 2280 (2.2 KB)
+ TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
  
  lo: flags=73  mtu 65536
- inet 127.0.0.1  netmask 255.0.0.0
- inet6 ::1  prefixlen 128  scopeid 0x10
- loop  txqueuelen 1000  (Local Loopback)
- RX packets 200  bytes 16052 (16.0 KB)
- RX errors 0  dropped 0  overruns 0  frame 0
- TX packets 200  bytes 16052 (16.0 KB)
- TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
+ inet 127.0.0.1  netmask 255.0.0.0
+ inet6 ::1  prefixlen 128  scopeid 0x10
+ loop  txqueuelen 1000  (Local Loopback)
+ RX packets 200  bytes 16052 (16.0 KB)
+ RX errors 0  dropped 0  overruns 0  frame 0
+ TX packets 200  bytes 16052 (16.0 KB)
+ TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
  
- $ping -c 10 -I ens8 11.141.20.8 
+ $ping -c 10 -I ens8 11.141.20.8
  PING 11.141.20.8 (11.141.20.8) from 11.141.20.8 ens8: 56(84) bytes of data.
  ^C
  --- 11.141.20.8 ping statistics ---
  3 packets transmitted, 0 received, 100% packet loss, time 2050ms
  
- $ping -c 10 -I ens3 10.141.20.8 
+ $ping -c 10 -I ens3 

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

[Talat Batheesh]

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:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678585/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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] TSO doesn't work properly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678585/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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:~# ethtool -i eno2
driver: igb
version: 5.4.0-k
firmware-version: 1.63, 0x89fa
expansion-rom-version:
bus-info: :06:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: no

3.
root:~# ethtool -k eno2 | grep offload
tcp-segmentation-offload: on
udp-fragmentation-offload: off [fixed]
generic-segmentation-offload: on
generic-receive-offload: on
large-receive-offload: off [fixed]
rx-vlan-offload: on
tx-vlan-offload: on
l2-fwd-offload: off [fixed]
hw-tc-offload: off [fixed]

4.
root@:~# ethtool -K eno2 gso off

5.
root@:~# ethtool -k eno2 | grep offload
tcp-segmentation-offload: on
udp-fragmentation-offload: off [fixed]
generic-segmentation-offload: off
generic-receive-offload: on
large-receive-offload: off [fixed]
rx-vlan-offload: on
tx-vlan-offload: on
l2-fwd-offload: off [fixed]
hw-tc-offload: off [fixed]

6.
netperf -H 10.195.43.1 -l 4 -t TCP_STREAM -c -C -- -m 15000
Traffic size less or equal to 1514 is observed, despite the fact TSO is on.

7.
ethtool -K eno2 tso on

8.
netperf -H 10.195.43.1 -l 4 -t TCP_STREAM -c -C -- -m 15000
Traffic size of 64K is observed.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678585/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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 - stack corruption when trying to copy
  20 bytes to a sockaddr

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1668042/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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
only when linking is true. Otherwise it should be ignored.

Fixes: 7907f23adc18 (net/mlx5: Implement RoCE LAG feature)
Signed-off-by: Talat Batheesh <tal...@mellanox.com>
Reviewed-by: Aviv Heller <av...@mellanox.com>
Reviewed-by: Moni Shoua <mo...@mellanox.com>
Signed-off-by: Saeed Mahameed <sae...@mellanox.com>
Signed-off-by: David S. Miller <da...@davemloft.net>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1676786

Title:
  [Zesty] mlx5_core Kernel oops with bonding mode 1 and 6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1676786/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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

** Description changed:

  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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1676858

Title:
  [zesty] mlx4_core OOM with 32 bit arch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1676858/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1676857

Title:
  [zesty] mlx4_core OOM with 32 bit arch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1676857/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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 attrs even if mode_get op does not 
exist
1a6aa36 devlink: use nla_put_failure goto label instead of out
21e3d2d devlink: rename devlink_eswitch_fill to devlink_nl_eswitch_fill
adf200f devlink: fix the name of eswitch commands
65ba8fb net/mlx5e: Avoid wrong identification of rules on deletion

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1676388

Title:
  [zesty] mlx5e OVS fixes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1676388/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

Public bug reported:

We get kernel panic when we install a bond interface with two of
Mellanox mlx5 NIC's and try to unload the bonding module.

scenario:
1. network interfaces configuration 
# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

 # The loopback network interface
 auto lo
 iface lo inet loopback

 # The primary network interface
 auto eno1
 iface eno1 inet dhcp

 #ens1f0
 auto ens1f0
 iface ens1f0 inet manual
 bond-master bond1

 auto ens1f1
 iface ens1f1 inet manual
 bond-master bond1

 auto bond1
 iface bond1 inet static
 address 27.65.194.1
 netmask 255.255.255.0
 bond-slaves ens1f0 ens1f1
 bond-mode 1
 bond-primary ens1f0
 bond-miimon 100
 iface bond1 inet6 static
 address 907c:c828:4d05:5bf8::::0002/127  

# cat /etc/modprobe.d/bonding.conf
options bonding mode=1


2. ifup bond1 
3. modprobe -r bonding 

4. OOPS
Mar 12 16:44:32 qa-h-vrt-038 kernel: [  540.443796] Oops:  [#1] SMP 
 
Mar 12 16:44:32 qa-h-vrt-038 kernel: [  540.444686] Modules linked in: mlx5_ib 
mlx5_core bonding mlx4_ib ib_core mlx4_en mlx4_core nfsv3 nfs fscache 
xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat 
nf_nat_ipv4 nf_nat libcrc32c nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack 
nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter 
ebtables ip6table_filter ip6_tables iptable_filter ipmi_ssif intel_rapl sb_edac 
edac_core x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm 
irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel 
aes_x86_64 crypto_simd glue_helper cryptd intel_cstate joydev input_leds 
intel_rapl_perf serio_raw lpc_ich hpilo ipmi_si ioatdma ipmi_devintf dca 
ipmi_msghandler shpchp mac_hid acpi_power_meter nfsd auth_rpcgss nfs_acl lockd 
grace sunrpc ip_tables  
 
Mar 12 16:44:32 qa-h-vrt-038 kernel: [  540.469445]  x_tables autofs4 
hid_generic psmouse usbhid hid pata_acpi tg3 hpsa ptp scsi_transport_sas 
devlink pps_core wmi fjes [last unloaded: mlx5_core]


 
Mar 12 16:44:32 qa-h-vrt-038 kernel: [  540.473672] CPU: 23 PID: 4846 Comm: 
ifenslave Not tainted 4.10.0-9-generic #11-Ubuntu   
  
Mar 12 16:44:32 qa-h-vrt-038 kernel: [  540.475894] Hardware name: HP ProLiant 
DL380p Gen8, BIOS P70 07/01/2015
   
Mar 12 16:44:32 qa-h-vrt-038 kernel: [  540.478038] task: 9b8394e31680 
task.stack: b2ed054f4000
   
Mar 12 16:44:32 qa-h-vrt-038 kernel: [  540.533408] RIP: 
0010:mlx5_lag_netdev_event+0x1e6/0x230 [mlx5_core]  
 
Mar 12 16:44:32 qa-h-vrt-038 kernel: [  540.590069] RSP: 0018:b2ed054f7bd0 
EFLAGS: 00010202
Mar 12 16:44:32 qa-h-vrt-038 kernel: [  540.646302] RAX: 0002 RBX: 
9b7f825f6000 RCX: 
Mar 12 16:44:32 qa-h-vrt-038 kernel: [  540.701966] RDX:  RSI: 
00040400 RDI: 9b7f840a00b0
Mar 12 16:44:32 qa-h-vrt-038 kernel: [  540.756395] RBP: b2ed054f7c18 R08: 
c02fb000 R09: 9b7fa3117ea8
Mar 12 16:44:32 qa-h-vrt-038 kernel: [  540.810250] R10:  R11: 
0051a84e R12: 0001
Mar 12 16:44:32 qa-h-vrt-038 kernel: [  540.863569] R13: 0004 R14: 
9b7fa3117ea8 R15: 8992b108
Mar 12 16:44:32 qa-h-vrt-038 kernel: [  540.916725] FS:  7fc6cca0e700() 
GS:9b83af0c() knlGS:
Mar 12 16:44:32 qa-h-vrt-038 kernel: [  541.020509] CS:  0010 DS:  ES:  
CR0: 80050033
Mar 12 16:44:32 qa-h-vrt-038 kernel: [  541.072342] CR2: 0002 CR3: 
000817013000 CR4: 001406e0
Mar 12 16:44:32 qa-h-vrt-038 kernel: [  541.127206] Call Trace:
Mar 12 16:44:32 qa-h-vrt-038 kernel: [  541.180602]  
notifier_call_chain+0x4a/0x70
Mar 12 16:44:32 qa-h-vrt-038 kernel: [  541.235310]  
raw_notifier_call_chain+0x16/0x20
Mar 12 16:44:32 qa-h-vrt-038 kernel: [  541.287923]  
call_netdevice_notifiers_info+0x35/0x60
Mar 12 16:44:32 qa-h-vrt-038 kernel: [  541.342951]  
netdev_upper_dev_unlink+0x72/0xb0
Mar 12 16:44:32 qa-h-vrt-038 kernel: [  541.395322]  
bond_upper_dev_unlink.isra.42+0x18/0x40 [bonding]
Mar 12 16:44:32 qa-h-vrt-038 kernel: [  541.446520]  
__bond_release_one+0x170/0x550 [bonding]
Mar 12 16:44:32 qa-h-vrt-038 kernel: [  541.499303]  ? 

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

[Talat Batheesh]

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 ens5f0 ingress
tc qdisc add dev ens5f0 ingress

tc filter add dev ens5f0 parent : protocol ip pref 8 handle 0x1 flower 
dst_mac e4:1d:2d:5d:25:35 ip_proto udp src_port 2009 action mirred egress 
redirect dev eth0
tc filter add dev ens5f0 parent : protocol arp pref 1 handle 0x1 flower 
dst_mac e4:1d:2d:5d:25:35 src_mac e4:1d:2d:5d:25:34 action mirred egress 
redirect dev eth0
tc filter del dev ens5f0 parent : pref 8 handle 0x1 flower
tc filter add dev ens5f0 parent : protocol ip pref 4 handle 0x1 flower 
dst_mac e4:1d:2d:5d:25:35 src_mac e4:1d:2d:5d:25:34 ip_proto udp src_port 2229 
action mirred egress redirect dev eth0
tc filter add dev ens5f0 parent : protocol ip pref 8 handle 0x1 flower 
dst_mac e4:1d:2d:5d:25:35 ip_proto udp src_port 2009 action mirred egress 
redirect dev eth0


2. DELETE_VXLAN_UDP_DPORT failed when restart ovs in vxlan with non-
default port

- configure ovs - vxlan with non-default port (1236)
- service openvswitch restart


The Following commits should fix those issue

Commit ID: 1ad9a00ae0efc2e9337148d6c382fad3d27bf99a
Title: net/mlx5e: Avoid supporting udp tunnel port ndo for VF reps
Link: 
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=1ad9a00ae0efc2e9337148d6c382fad3d27bf99a


Commit ID: af36370569eb37420e1e78a2e60c277b781fcd00
Title: net/mlx5: Fix create autogroup prev initializer
Like: 
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=af36370569eb37420e1e78a2e60c277b781fcd00

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1676388

Title:
  [zesty] mlx5e OVS fixes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1676388/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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:
  ifup service of network device stay active after driver stop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672144/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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 about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672144/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

This bug reproduced with tg3 , mlx4, mlx5 and bonding modules and i
beleve that this issue reproduce on each interface that has ifup
service.

simple reproduce 
1. interfaces is up after reboot or ifup.
2. modprobe -r 
#network interfaces closed and removed
3.systemctl status ifup@.service
# 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/bugs/1672144

Title:
  ifup service of network device stay active after driver stop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1672144/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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 to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1672144/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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 environments

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1673491/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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
After=local-fs.target network-pre.target apparmor.service systemd-sysctl.service
Before=network.target shutdown.target network-online.target
Conflicts=shutdown.target
BindsTo=sys-subsystem-net-devices-%i.device
After=sys-subsystem-net-devices-%i.device
DefaultDependencies=no
IgnoreOnIsolate=yes

[Service]
# avoid stopping on shutdown via stopping system-ifup.slice
Slice=system.slice
ExecStart=/bin/sh -ec 'ifup --allow=hotplug %I; ifup --allow=auto %I; \
if ifquery %I >/dev/null; then ifquery --state %I >/dev/null; fi'
ExecStop=/sbin/ifdown %I
RemainAfterExit=true
TimeoutStartSec=5min

-- 
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 to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1672144/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674087/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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, etc.


Sample exercise(showing variable length use of cookie)

.. create an accept action with cookie a1b2c3d4
sudo $TC actions add action ok index 1 cookie a1b2c3d4

.. dump all gact actions..
sudo $TC -s actions ls action gact

action order 0: gact action pass
 random type none pass val 0
 index 1 ref 1 bind 0 installed 5 sec used 5 sec
Action statistics:
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
cookie a1b2c3d4

.. bind the accept action to a filter..
sudo $TC filter add dev lo parent : protocol ip prio 1 \
u32 match ip dst 127.0.0.1/32 flowid 1:1 action gact index 1

... send some traffic..
$ ping 127.0.0.1 -c 3
PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.020 ms
64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.027 ms
64 bytes from 127.0.0.1: icmp_seq=3 ttl=64 time=0.038 ms


upstream Commits 
1045ba7 net sched actions: Add support for user cookies
37f1c63 net sched actions: do not overwrite status of action creation.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674087/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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://bugs.launchpad.net/bugs/1673491

Title:
  [Zesty] libnl3 Segmentation fault in sriov environments

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1673491/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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 because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1673491

Title:
  [Zesty] libvirtd  Segmentation fault after running virt-manager

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1673491/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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 gdb (Ubuntu 7.12.50.20170314-0ubuntu1) 7.12.50.20170314-git
Copyright (C) 2017 Free Software Foundation, Inc.  
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.   
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"   
and "show warranty" for details. 
This GDB was configured as "x86_64-linux-gnu".   
Type "show configuration" for configuration details. 
For bug reporting instructions, please see:  
. 
Find the GDB manual and other documentation resources online at: 
.
For help, type "help".   
Type "apropos word" to search for commands related to "word"...  
Reading symbols from /usr/sbin/libvirtd...(no debugging symbols found)...done.
[New LWP 4232]
[New LWP 4216]
[New LWP 4219]
[New LWP 4218]
[New LWP 4231]
[New LWP 4215]
[New LWP 4220]
[New LWP 4224]
[New LWP 4221]
[New LWP 4223]
[New LWP 4222]
[New LWP 4217]
[New LWP 4225]
[New LWP 4227]
[New LWP 4230]
[New LWP 4229]
[New LWP 4228]
[Thread debugging using libthread_db enabled] 
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/sbin/libvirtd'.   
Program terminated with signal SIGSEGV, Segmentation fault.   
#0  0x7f97fa93367f in rtnl_link_sriov_parse_vflist () from 
/usr/lib/x86_64-linux-gnu/libnl-route-3.so.200
[Current thread is 1 (Thread 0x7f97dff94700 (LWP 4232))]
 
(gdb) where 
 
#0  0x7f97fa93367f in rtnl_link_sriov_parse_vflist () from 
/usr/lib/x86_64-linux-gnu/libnl-route-3.so.200
#1  0x7f97fa927fad in ?? () from 
/usr/lib/x86_64-linux-gnu/libnl-route-3.so.200  
#2  0x7f980bfb76c3 in nl_cache_parse () from 
/lib/x86_64-linux-gnu/libnl-3.so.200
#3  0x7f980bfb770b in ?? () from /lib/x86_64-linux-gnu/libnl-3.so.200   
 
#4  0x7f980bfbdc1c in nl_recvmsgs_report () from 
/lib/x86_64-linux-gnu/libnl-3.so.200
#5  0x7f980bfbe049 in nl_recvmsgs () from 
/lib/x86_64-linux-gnu/libnl-3.so.200   
#6  0x7f980bfb6aab in ?? () from /lib/x86_64-linux-gnu/libnl-3.so.200   
 
#7  0x7f980bfb763d in nl_cache_pickup () from 
/lib/x86_64-linux-gnu/libnl-3.so.200   
#8  0x7f980bfb7871 in nl_cache_refill () from 
/lib/x86_64-linux-gnu/libnl-3.so.200   
#9  0x7f97fa926975 in rtnl_link_alloc_cache_flags () from 
/usr/lib/x86_64-linux-gnu/libnl-route-3.so.200 
#10 0x7f97fb224aff in ?? () from /usr/lib/x86_64-linux-gnu/libnetcf.so.1
 
#11 0x7f97fb225e57 in ?? () from /usr/lib/x86_64-linux-gnu/libnetcf.so.1
 
#12 0x7f97fb43699a in ?? () from 
/usr/lib/libvirt/connection-driver/libvirt_driver_interface.so  
#13 0x7f980d1414cf in virStateInitialize () from 
/usr/lib/x86_64-linux-gnu/libvirt.so.0  
#14 

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

[Talat Batheesh]

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 didn't see the 
interface with the static configuration =.
below simple reproduce with the Mellanox ConnectX4 device (driver name 
mlx5_core).

Also we see this issue with Azure system, Ubuntu 17.04 guest over
Hyper-v, the  VF failed to start after re-enable SR-IOV from VM's vNIC.


For now we have a Work Around that to add a udev rule,
 echo DRIVERS==\"*mlx*\", SUBSYSTEM==\"net\", 
ACTION==\"add\",RUN+=\"/sbin/ifup --force $env{INTERFACE}\" > 
/lib/udev/rules.d/100-up.rules
Example:
#:/lib/udev/rules.d# cat 100-up.rules
DRIVERS=="*mlx*", SUBSYSTEM=="net", ACTION=="add",RUN+="/sbin/ifup --force 
$env{INTERFACE}" 

***
* More info and reproduce *
***
# ifdown ens1f0
RTNETLINK answers: Cannot assign requested address
# ifup ens1f0 
# ifconfig ens1f0 
ens1f0: flags=4163  mtu 1500
inet 123.12.23.1  netmask 255.255.0.0  broadcast 123.12.255.255
inet6 fe80::268a:7ff:fea1:fbdc  prefixlen 64  scopeid 0x20
ether 24:8a:07:a1:fb:dc  txqueuelen 1000  (Ethernet)
RX packets 0  bytes 0 (0.0 B)   
RX errors 0  dropped 0  overruns 0  frame 0 
TX packets 17  bytes 1392 (1.3 KB)  
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0  

# ethtool -i ens1f0 |grep driv
driver: mlx5_core
# systemctl status ifup@ens1f 
ifup@ens1f0.service  ifup@ens1f1.service

# systemctl status ifup@ens1f0.service 
* ifup@ens1f0.service - ifup for ens1f0  
   Loaded: loaded (/lib/systemd/system/ifup@.service; static; vendor preset: 
enabled)
   Active: active (exited) since Sun 2017-03-12 09:40:04 IST; 2h 26min ago  
 
 Main PID: 1608 (code=exited, status=0/SUCCESS) 
 
   CGroup: /system.slice/ifup@ens1f0.service
 

Mar 12 09:40:04 qa-h-vrt-039 systemd[1]: Started ifup for ens1f0.
Mar 12 09:40:04 qa-h-vrt-039 sh[1608]: ifup: interface ens1f0 already configured
root@qa-h-vrt-039:/tmp# modprobe -rv mlx5_ib 
rmmod mlx5_ib
rmmod mlx5_core  

# modprobe -rv mlx5_core

# ifconfig -a |grep ens1f0

# lsmod |grep mlx5

# systemctl status ifup@ens1f0.service
* ifup@ens1f0.service - ifup for ens1f0 
   Loaded: loaded (/lib/systemd/system/ifup@.service; static; vendor preset: 
enabled)
   Active: active (exited) since Sun 2017-03-12 09:40:04 IST; 2h 27min ago
 Main PID: 1608 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/ifup@ens1f0.service

Mar 12 09:40:04 qa-h-vrt-039 systemd[1]: Started ifup for ens1f0.
Mar 12 09:40:04 qa-h-vrt-039 sh[1608]: ifup: interface ens1f0 already configured

# modprobe mlx5_core

# ifconfig ens1f0
ens1f0: flags=4098  mtu 1500
ether 24:8a:07:a1:fb:dc  txqueuelen 1000  (Ethernet)
RX packets 0  bytes 0 (0.0 B)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 0  bytes 0 (0.0 B)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).


# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eno1
iface eno1 inet dhcp

#ens1f0
auto ens1f0
iface ens1f0 inet static
address 123.12.23.1
netmask 255.255.0.0
mtu 1500


*
* Another repto and investigate *
*
once interface is created the system starts a service that is responsible for 
activating it (basically runs ifup).
so, at first shot everything works.
at the second driver reload:
Good flow (on good setup 4.9.0-rc5+):
1. driver is unloaded and the interface’s “ifup” service is shutdown:
Feb 23 00:54:09 reg-l-vrt-206-006 kernel: [6.790189] mlx4_en: enP43508p0s2: 
Close port called
Feb 23 00:54:09 reg-l-vrt-206-006 kernel: [6.868484] hv_netvsc 
a2be13bb-7244-44ff-a31a-dea8d58a79da eth1: VF down: enP43508p0s2
Feb 23 00:54:09 reg-l-vrt-206-006 kernel: [6.868487] hv_netvsc 
a2be13bb-7244-44ff-a31a-dea8d58a79da eth1: Data path switched from VF: 
enP43508p0s2
Feb 23 00:54:09 reg-l-vrt-206-006 kernel: [6.869575] hv_netvsc 
a2be13bb-7244-44ff-a31a-dea8d58a79da eth1: VF unregistering: enP43508p0s2
Feb 23 00:54:09 reg-l-vrt-206-006 systemd1: Stopping ifup for enP43508p0s2...
Feb 23 00:54:09 reg-l-vrt-206-006 ifdown47196: Cannot find device 
"enP43508p0s2" 
Feb 23 00:54:09 reg-l-vrt-206-006 

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

[Talat Batheesh]

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:
  iproute2: range error adding rules from tc

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1669317/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

** 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.
https://bugs.launchpad.net/bugs/1669317

Title:
  iproute2: range error adding rules from tc

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1669317/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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 

   
RTNETLINK answers: Numerical result out of range   

iproute2 is the newest version (4.9.0-1ubuntu1).

The fix is already upstream.
Attached fix.

** Affects: iproute2 (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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:
  iproute2: range error adding rules from tc

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1669317/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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 when trying to copy
  20 bytes to a sockaddr

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1668042/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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 member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1668042

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1668042/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1668019/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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 ]Bonding driver - stack corruption when trying to copy
  20 bytes to a sockaddr

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1668042/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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 ("net/bonding: Enable bonding to enslave
netdevices not supporting set_mac_address()") was introduced till
4.7-rc1, IPoIB didn't support the set_mac_address ndo, and hence the
fail over mac policy always applied to IPoIB bonds.

With the introduction of commit 492a7e67ff83 ("IB/IPoIB: Allow setting
the device address"), that doesn't hold and practically IPoIB bonds are
broken as of that. To fix it, lets go to fail over mac if the device
doesn't support the ndo OR this is IPoIB device.

As a by-product, this commit also prevents a stack corruption which
occurred when trying to copy 20 bytes (IPoIB) device address
to a sockaddr struct that has only 16 bytes of storage.


[1]
Get panic after create bond with down/updelay and restart NIC driver
Configure bond with down/updelay

cat /etc/network/interfaces
auto bond1
iface bond1 inet static
address 31.136.42.17
netmask 255.255.0.0
bond-slaves ib0 ib1
bond-miimon 100
bond-updelay 5000
bond-mode active-backup
bond-primary ib1
bond-downdelay 5000

auto ib0
iface ib0 inet manual
bond-master bond1

auto ib1
iface ib1 inet manual
bond-master bond1

modprobe -r 


[2]
1533e77315220dc1d5ec3bd6d9fe32e2aa0a74c0
net/bonding: Enforce active-backup policy for IPoIB bonds

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: 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 - stack corruption when trying to copy
  20 bytes to a sockaddr

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1668042/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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 should improve the OVS offload driver:

PICK: 5cecb6c net/sched: cls_bpf: Reflect HW offload status
PICK: 24d3dc6 net/sched: cls_u32: Reflect HW offload status
PICK: c7d2b2f net/sched: cls_matchall: Reflect HW offloading status
PICK: 5559396 net/sched: cls_flower: Reflect HW offload status
PICK: e696028 net/sched: Reflect HW offload status
PICK: 7a335ad net/sched: cls_matchall: Dump the classifier flags
PICK: 749e672 net/sched: cls_flower: Properly handle classifier flags 
dumping
PICK: a61d5ce net/mlx5: Fix static checker warnings
PICK: 264d7bf net/mlx5: E-Switch, Enlarge the FDB size for the switchdev 
mode
PICK: ce99f6b net/mlx5e: Support SRIOV TC encapsulation offloads for IPv6 
tunnels
PICK: 9a94111 net/mlx5e: Maximize ip tunnel key usage on the TC offloading 
path
PICK: 76f7444 net/mlx5e: Use the full tunnel key info for encapsulation 
offload house-keeping
PICK: 75c33da net/mlx5e: TC ipv4 tunnel encap offload cosmetic changes
PICK: 19f4440 net/mlx5e: Add TC offloads matching on IPv6 encapsulation 
headers
PICK: 073ff3c net/mlx5: Use exact encap header size for the FW input buffer
PICK: 7898489 IB/mlx5: Enable Eth VFs to query their min-inline value for 
user-space
PICK: 8c7245a6 net/mlx5: Push min-inline mode resolution helper into the 
core
PICK: a3308d8 net/sched: cls_flower: Disallow duplicate internal elements

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: zesty

-- 
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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1668019/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

** 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 about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649207/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

Public bug reported:

Failed to increase rx ring to 4096 - SIOCSIFFLAGS: Cannot allocate
memory

Scenario

ubuntu@cto-netsim3:~$ sudo ethtool -g ens6f0
[sudo] password for ubuntu:
Ring parameters for ens6f0:
Pre-set maximums:
RX: 4096
RX Mini: 0
RX Jumbo: 0
TX: 8192
Current hardware settings:
RX: 1024
RX Mini: 0
RX Jumbo: 0
TX: 1024

ubuntu@cto-netsim3:~$ sudo ethtool -G ens6f0 rx 4096
Cannot set device ring parameters: Cannot allocate memory

After brinding the interface down with:

ubuntu@cto-netsim3:~$ sudo ifconfig ens6f0 down

I can not bring it back up !!!

ubuntu@cto-netsim3:~$ sudo ifconfig ens6f0 up
SIOCSIFFLAGS: Cannot allocate memory
ubuntu@cto-netsim3:~$
ubuntu@cto-netsim3:~$
ubuntu@cto-netsim3:~$ sudo ifconfig ens6f0 up
SIOCSIFFLAGS: Cannot allocate memory
ubuntu@cto-netsim3:~$
ubuntu@cto-netsim3:~$
ubuntu@cto-netsim3:~$ sudo ifconfig ens6f0 up
SIOCSIFFLAGS: Cannot allocate memory
ubuntu@cto-netsim3:~$
ubuntu@cto-netsim3:~$
ubuntu@cto-netsim3:~$ sudo ifconfig ens6f0 up
SIOCSIFFLAGS: Cannot allocate memory
ubuntu@cto-netsim3:~$
ubuntu@cto-netsim3:~$
ubuntu@cto-netsim3:~$ sudo ifconfig ens6f0 up
SIOCSIFFLAGS: Cannot allocate memory
ubuntu@cto-netsim3:~$
ubuntu@cto-netsim3:~$ sudo ifconfig ens6f0 up
SIOCSIFFLAGS: Cannot allocate memory
ubuntu@cto-netsim3:~$
ubuntu@cto-netsim3:~$
ubuntu@cto-netsim3:~$ sudo ifconfig ens6f0 up
SIOCSIFFLAGS: Cannot allocate memory
ubuntu@cto-netsim3:~$
ubuntu@cto-netsim3:~$
ubuntu@cto-netsim3:~$ sudo ifconfig ens6f0 up
SIOCSIFFLAGS: Cannot allocate memory
ubuntu@cto-netsim3:~$
ubuntu@cto-netsim3:~$
ubuntu@cto-netsim3:~$ sudo ifconfig ens6f0 up
SIOCSIFFLAGS: Cannot allocate memory
ubuntu@cto-netsim3:~$
ubuntu@cto-netsim3:~$
ubuntu@cto-netsim3:~$ sudo ifconfig ens6f0 up
SIOCSIFFLAGS: Cannot allocate memory
ubuntu@cto-netsim3:~$

dmsg:
[ 774.935067] mlx5_core :81:00.0: swiotlb buffer is full (sz: 8388608 bytes)
[ 774.935070] swiotlb: coherent allocation failed for device :81:00.0 
size=8388608
[ 774.935074] CPU: 38 PID: 6042 Comm: ethtool Not tainted 4.8.0-22-generic #24
[ 774.935075] Hardware name: Quanta Computer Inc D51B-1U (dual 1G LoM)/S2B-MB 
(dual 1G LoM), BIOS S2B_3A19 05/15/2015
[ 774.935078] 0286 65a68699 8d946b1db9a0 
8502f5d2
[ 774.935083]  007f 8d946b1db9e8 
8505a280
[ 774.935087] 8d946b1dba80 8d94000b 024082c0 
8db471b0e0a0
[ 774.935091] Call Trace:
[ 774.935104] [] dump_stack+0x63/0x81
[ 774.935108] [] swiotlb_alloc_coherent+0x140/0x160
[ 774.935115] [] x86_swiotlb_alloc_coherent+0x43/0x50
[ 774.935150] [] mlx5_dma_zalloc_coherent_node+0xa4/0x100 
[mlx5_core]
[ 774.935164] [] mlx5_buf_alloc_node+0x4d/0xc0 [mlx5_core]
[ 774.935181] [] mlx5_cqwq_create+0x7e/0x160 [mlx5_core]
[ 774.935199] [] mlx5e_open_cq+0x9e/0x1f0 [mlx5_core]
[ 774.935214] [] mlx5e_open_channels+0x715/0xf30 [mlx5_core]
[ 774.935229] [] mlx5e_open_locked+0xda/0x1e0 [mlx5_core]
[ 774.935245] [] mlx5e_set_ringparam+0x21e/0x350 [mlx5_core]
[ 774.935252] [] dev_ethtool+0x59f/0x1fc0
[ 774.935255] [] ? new_slab+0x300/0x6e0
[ 774.935259] [] ? __rtnl_unlock+0x2a/0x50
[ 774.935262] [] ? netdev_run_todo+0x60/0x330
[ 774.935266] [] ? alloc_set_pte+0x4ec/0x610
[ 774.935268] [] ? dev_get_by_name_rcu+0x61/0x80
[ 774.935272] [] dev_ioctl+0x180/0x5a0
[ 774.935277] [] sock_do_ioctl+0x42/0x50
[ 774.935280] [] sock_ioctl+0x1d2/0x290
[ 774.935283] [] do_vfs_ioctl+0xa3/0x610
[ 774.935287] [] ? __do_page_fault+0x203/0x4d0
[ 774.935289] [] SyS_ioctl+0x79/0x90
[ 774.935307] [] entry_SYSCALL_64_fastpath+0x1e/0xa8
[ 774.935312] mlx5_core :81:00.0: :81:00.0:mlx5_cqwq_create:121:(pid 
6042): mlx5_buf_alloc_node() failed, -12
[ 774.935537] mlx5_core :81:00.0 ens6f0: mlx5e_open_locked: 
mlx5e_open_channels failed, -12


This is the upstream patches that fix this issue 
ec8b9981ad3f net/mlx5e: Create UMR MKey per RQ
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, 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 about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649207/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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

Title:
  PPC + kernel 4.8 swap_dup: Bad swap file entry 2c16ed28

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634862/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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 about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634862/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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 in the 
/etc/network/interfaces to be 1500 the interface get back to work.

root:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.10
Release:16.10
Codename:   yakkety
root:~# uname -r
4.8.0-26-generic


scenario: 
set the MTU static to 67 

root:~# ifdown ens2
root:~# ifup ens2
root:~# ifdown ens2
RTNETLINK answers: No such device
root:~# ifup ens2
RTNETLINK answers: No buffer space available
Failed to bring up ens2.
root:~# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

auto ens2
iface ens2 inet static
address 21.3.5.16
mtu 67

## change MTU static to 1500 
root:~# vim /etc/network/interfaces
root:~# ifdown ens2
ifdown: interface ens2 not configured
root:~# ifup ens2
RTNETLINK answers: No buffer space available
Failed to bring up ens2.

root:~# ip link set ens2 mtu 1500
root:~# ifup ens2

** Affects: ifupdown (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1638256

Title:
  ifup fail when use MTU small than 68

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1638256/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

Hi Joseph,
we already test the following kernel and here is the status.

v4.8-rc8 http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8-rc8/ working 
v4.8-rc1 http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8-rc1/  working 
v4.8 http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8/  not working 


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 2c16ed28

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634862/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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 
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 about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634862/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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 and pages of the following showing, this is 
just a sample from the system log.
I had been running with kernel 4.4 and everything worked ok on the same 
machine, so when we upgrade to kernel 4.8 we start to see the following error 

dmseg log gets lots of this message:

-
[10101.785548] swap_dup: Bad swap file entry 2c16ed28
[10101.785595] swap_dup: Bad swap file entry 2c16ed29
[10101.785606] swap_dup: Bad swap file entry 2c16ed2a
[10101.785613] swap_dup: Bad swap file entry 2c16ed2b
[10101.785622] swap_dup: Bad swap file entry 2c16ed2c
[10101.785629] swap_dup: Bad swap file entry 2c16ed2d
[10101.785637] swap_dup: Bad swap file entry 2c16ed2e
[10101.785648] swap_dup: Bad swap file entry 2c16ed2f
[10101.785659] swap_dup: Bad swap file entry 2c16ed2e   and call trace 
: 
Call Trace:  
[10101.785773] [c002fb923ac0] [c0b9db00] dump_stack+0xb0/0xf0 
(unreliable)  
[10101.785789] [c002fb923b00] [c0b9b330] dump_header+0x84/0x224 

[10101.785801] [c002fb923bd0] [c025d724] 
oom_kill_process+0x3b4/0x5c0   
[10101.785811] [c002fb923c80] [c025dc80] out_of_memory+0x290/0x580  

[10101.785822] [c002fb923d30] [c025dff4] 
pagefault_out_of_memory+0x84/0xb0  
[10101.785836] [c002fb923d80] [c0b94d44] do_page_fault+0x7c4/0x7d0  

[10101.785849] [c002fb923e30] [c0008948] 
handle_page_fault+0x10/0x30   


# cat /etc/*-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.10
DISTRIB_CODENAME=yakkety
DISTRIB_DESCRIPTION="Ubuntu 16.10"
NAME="Ubuntu"
VERSION="16.10 (Yakkety Yak)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.10"
VERSION_ID="16.10"
HOME_URL="http://www.ubuntu.com/;
SUPPORT_URL="http://help.ubuntu.com/;
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
PRIVACY_POLICY_URL="http://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
VERSION_CODENAME=yakkety
UBUNTU_CODENAME=yakkety

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "full dmesg"
   
https://bugs.launchpad.net/bugs/1634862/+attachment/4763753/+files/full_dmesg.txt

-- 
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 about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634862/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/srptools/+bug/1565649/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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 vlan over VxLan

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1477466/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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.
https://bugs.launchpad.net/bugs/1477466

Title:
  Low performance when using vlan over VxLan

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1477466/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1585978] Re: mlx5_core kexec fail

[Talat Batheesh]

** 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 this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1585978/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

** 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 manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1528466/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1585978] [NEW] mlx5_core kexec fail

[Talat Batheesh]

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 
--initrd=/boot/initramfs-4.3.0-rc6-gemini-perf-2015-10-22_19-44-01.img 
--command-line="root=UUID=7ec1922f-8631-46bf-abe4-afb7affab4fe console=tty0 
console=ttyS0,115200n8 rhgb SYSFONT=latarcyrheb-sun16 LANG=en_US.UTF-8 
KEYTABLE=us"  

# kexec -e


upstream commit that fix this issue 
commit 5fc7197d3a256d9c5de3134870304b24892a4908
Author: Majd Dibbiny    
Date:   Fri Apr 22 00:33:07 2016 +0300 

net/mlx5: Add pci shutdown callback

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Incomplete


** Tags: 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 this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1585978/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

Hi,

This Fix is for old releases that doesn't include mlx4_en in their initramfs.
Now, that the initrd include the mlx4_en, so no need to creating a mlx4.conf 
file with softdep mlx4_core post: mlx4_en
After removing this file we see that mlx4_en loaded after boot due to mlx4_core 
request a module according to the port type -

drivers/net/ethernet/mellanox/mlx4/main.c
static void mlx4_request_modules(struct mlx4_dev *dev)
{
int port;
int has_ib_port = false;
int has_eth_port = false;
#define EN_DRV_NAME "mlx4_en"
#define IB_DRV_NAME "mlx4_ib"

for (port = 1; port <= dev->caps.num_ports; port++) {
if (dev->caps.port_type[port] == MLX4_PORT_TYPE_IB)
has_ib_port = true;
else if (dev->caps.port_type[port] == MLX4_PORT_TYPE_ETH)
has_eth_port = true;
}

if (has_eth_port)
request_module_nowait(EN_DRV_NAME);
if (has_ib_port || (dev->caps.flags & MLX4_DEV_CAP_FLAG_IBOE))
request_module_nowait(IB_DRV_NAME);
}


We are debianize rdma-utils package that create a file 
/etc/modpobe.d/mlx4.conf, according to Debian policy  package shouldn't modify 
files installed by another package in any way, it's forbidden.
in addition the rdma service create the same file name and add the following 
install mlx4_core /sbin/modprobe --ignore-install mlx4_core && (if [ -f 
/usr/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 received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1115710

Title:
  Mellanox mlx4_en network driver is not automatically loaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1115710/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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 nexthdr.  On a little
endian systems shifting the byte is correct behavior, but it results in
incorrect csums on big endian architectures.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1544978

Title:
  PCI Call Traces  hw csum failure in dmesg with  4.4.0-2-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1544978/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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 4.1.0+1.46.gb1cdaf7-1ubuntu3_amd64.deb

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mstflint/+bug/1577164/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 6,640 B of archives.
After this operation, 14.3 kB of additional disk space will be used.
Get:1 http://webrepo/ubuntu-mirror xenial/universe amd64 mstflint amd64 
4.1.0+1.46.gb1cdaf7-1ubuntu3 [6,640 B]
Fetched 6,640 B in 0s (34.6 kB/s)
Selecting previously unselected package mstflint.
(Reading database ... 100297 files and directories currently installed.)
Preparing to unpack .../mstflint_4.1.0+1.46.gb1cdaf7-1ubuntu3_amd64.deb ...
Unpacking mstflint (4.1.0+1.46.gb1cdaf7-1ubuntu3) ...
Setting up mstflint (4.1.0+1.46.gb1cdaf7-1ubuntu3) ...

# mstflint
mstflint: command not found

# dpkg --list |grep mstflint
ii  mstflint   4.1.0+1.46.gb1cdaf7-1ubuntu3amd64
Mellanox firmware burning application

root@dev-h-vrt-006:~# dpkg-query -L mstflint
/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/mstflint
/usr/share/doc/mstflint/copyright
/usr/share/doc/mstflint/README.gz
/usr/share/doc/mstflint/changelog.Debian.gz
/usr/share/doc/mstflint/hca_self_test.readme


# uname -r
4.4.0-21-generic

** Affects: mstflint (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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 4.1.0+1.46.gb1cdaf7-1ubuntu3_amd64.deb

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mstflint/+bug/1577164/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

** 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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mstflint4/+bug/1470167/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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 support Mellanox ConnectX-4 HCAs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mstflint4/+bug/1470167/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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://bugs.launchpad.net/bugs/1565650

Title:
  add support for architectures ppc64el arm64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libibcm/+bug/1565650/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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.
https://bugs.launchpad.net/bugs/1565649

Title:
   add support for architectures ppc64el arm64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/srptools/+bug/1565649/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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 to Ubuntu.
https://bugs.launchpad.net/bugs/1529815

Title:
  InfiniBand DHCP flow with PRA and DHCP relay not working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1529815/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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"
HOME_URL="http://www.ubuntu.com/;
SUPPORT_URL="http://help.ubuntu.com/;
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
UBUNTU_CODENAME=xenial

# uname -a
Linux dev-h-vrt-006 4.4.0-11-generic #26-Ubuntu SMP Sat Mar 5 14:25:21 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux


#dmesg 
[174430.803529] mst_pci: module verification failed: signature and/or required 
key missing - tainting kernel   
  
[174453.001485] BUG: unable to handle kernel NULL pointer dereference at
   (null)   
 
[174453.001509] IP: [] mlx5e_set_coalesce+0x6e/0x100 
[mlx5_core] 
  
[174453.001535] PGD 81a5c7067 PUD 81aa93067 PMD 0   

 
[174453.001556] Oops:  [#1] SMP
[174453.001571] Modules linked in: mst_pciconf(OE) mst_pci(OE) nfsv3 nfs_acl 
rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache mlx5_ib ib_core 
ib_addr vfio_pci vfio_virqfd vfio_iommu_type1 vfio xt_CHECKSUM iptable_mangle 
ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT 
nf_reject_ipv4 xt_tcpudp ebtable_filter ebtables ip6table_filter ip6_tables 
iptable_filter ip_tables x_tables bridge stp llc x86_pkg_temp_thermal 
intel_powerclamp coretemp crct10dif_pclmul crc32_pclmul aesni_intel kvm_intel 
aes_x86_64 ipmi_ssif lrw gf128mul glue_helper ablk_helper cryptd serio_raw kvm 
sb_edac edac_core irqbypass hpilo ipmi_si 8250_fintek ioatdma ipmi_msghandler 
acpi_power_meter mac_hid lpc_ich shpchp sunrpc autofs4 mlx4_en
[174453.001928]  psmouse ixgbe dca vxlan pata_acpi ip6_udp_tunnel udp_tunnel 
mdio hpsa mlx5_core tg3 scsi_transport_sas mlx4_core ptp pps_core wmi fjes
[174453.002011] CPU: 2 PID: 40824 Comm: ethtool Tainted: G   OE   
4.4.0-11-generic #26-Ubuntu
[174453.002026] Hardware name: HP ProLiant DL380p Gen8, BIOS P70 12/20/2013
[174453.002037] task: 8800bd919b80 ti: 880814d74000 task.ti: 
880814d74000
[174453.002072] RIP: 0010:[]  [] 
mlx5e_set_coalesce+0x6e/0x100 [mlx5_core]
[174453.002119] RSP: 0018:880814d77c30  EFLAGS: 00010246
[174453.002141] RAX:  RBX: 880816e0 RCX: 

[174453.002176] RDX:  RSI: 880814d77c74 RDI: 
880814e6
[174453.002210] RBP: 880814d77c60 R08: 81e42520 R09: 
ff00
[174453.002245] R10: 0533 R11: 0246 R12: 
880814d77c74
[174453.002280] R13: 880814e6 R14:  R15: 
880814e6
[174453.002316] FS:  7f7e927f7700() GS:88081f68() 
knlGS:
[174453.002352] CS:  0010 DS:  ES:  CR0: 80050033
[174453.002374] CR2:  CR3: 000818365000 CR4: 
001406e0
[174453.002409] Stack:
[174453.002427]  17a4b290 880814e6 000600114bb3 
000f
[174453.002476]  8946 880814e6 880814d77ce0 
8171784a
[174453.002525]  000f0010 00200010  
00200010
[174453.002574] Call Trace:
[174453.002597]  [] ethtool_set_coalesce+0x5a/0x80
[174453.002621]  [] dev_ethtool+0xe78/0x1d70
[174453.002645]  [] ? page_cache_async_readahead+0x6b/0x70
[174453.002670]  [] ? page_add_file_rmap+0x25/0x60
[174453.002694]  [] ? __rtnl_unlock+0x15/0x20
[174453.002717]  [] ? netdev_run_todo+0x61/0x320
[174453.002741]  [] dev_ioctl+0x182/0x580
[174453.002765]  [] sock_do_ioctl+0x42/0x50
[174453.002788]  [] sock_ioctl+0x1d2/0x290
[174453.002811]  [] do_vfs_ioctl+0x29f/0x490
[174453.003136]  [] ? __do_page_fault+0x1b4/0x400
[174453.003161]  [] ? fd_install+0x25/0x30
[174453.003183]  [] SyS_ioctl+0x79/0x90
[174453.003208]  [] entry_SYSCALL_64_fastpath+0x16/0x71
[174453.003231] Code: 66 89 87 36 66 00 00 8b 46 08 66 89 87 38 66 00 00 0f 84 
91 00 00 00 49 89 fd 49 89 f4 48 63 45 d4 49 8b 95 00 13 00 00 45 31 f6 <4c> 8b 
3c c2 41 80 bf dc 18 00 00 00 74 3d 49 63 c6 41 0f b7 4c
[174453.003564] RIP  [] mlx5e_set_coalesce+0x6e/0x100 
[mlx5_core]
[174453.003607]  RSP 
[174453.003626] CR2: 
[174453.004055] ---[ end trace 8466dfbb422a27d8 ]---


Fix upstream commits
7524a5d88b94afef8397a79f1e664af5b7052c22 net/mlx5e: Don't modify CQ before it 
was created
2fcb92fbd04eef26dfe7e67839da6262d83d6b65 net/mlx5e: Don't try to modify CQ 
moderation if 

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

[Talat Batheesh]

** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1557950

Title:
  mlx5_core kernel trace after "ethtool -C eth1 adaptive-rx on" flow

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1557950/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

** 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 member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1557950

Title:
  mlx5_core kernel trace after "ethtool -C eth1 adaptive-rx on" flow

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1557950/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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  R2 with ConnectX3 FW ver 2.35.5000, WinOF 5.10 
   
SX GW, MLNX_OS ver 3.4.3002 


Looking at the traffic capture I can see packets are coming from the Windows 
server towards the switch, but never leaving it.
Please refer to the following traffic capture files attached to the case:
Ibdump_dhcp – capture of ib0
Dhcp.pcap – port mirroring of the ETH port connected to the Windows
Dhcp_win2012 - wireshark capture of the windows dhcp server 

Setup details is mentioned &  marked above.


Setup:
IB Side: DHCP Client  Ubunutu 14.04,   OFED 3.2-1.0.1.1,  CX3 2.35.5000 
(10.7.55.193)
ETH Side: DHCP Server Win2012 R2, WinOF 5.10,CX3 2.35.5000 
(10.7.55.190)
SX1036  GW:   MLNX_OS ver 3.4.3002

Before installing the PPA
DHCP client sends discover, DHCP server send offer, however the packet never 
reach the client, bootp flag is Unicast


** Attachment added: "dhcpcase files"
   
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1529815/+attachment/4597819/+files/dhcpcase.rar

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1529815

Title:
  InfiniBand DHCP flow with PRA and DHCP relay not working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1529815/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Talat Batheesh]

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:
  mstflint doesn't support Mellanox ConnectX-4 HCAs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mstflint/+bug/1470167/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs