This bug was fixed in the package dpdk - 17.11.5-0~ubuntu18.04.1
---
dpdk (17.11.5-0~ubuntu18.04.1) bionic; urgency=medium
* New upstream release 17.11.5; for a full list of changes see:
https://doc.dpdk.org/guides-17.11/rel_notes/release_17_11.html#id4
https://doc.dpdk.org/
This bug was fixed in the package dpdk - 17.11.5-0~ubuntu18.10.1
---
dpdk (17.11.5-0~ubuntu18.10.1) cosmic; urgency=medium
* New upstream release 17.11.5; for a full list of changes see:
https://doc.dpdk.org/guides-17.11/rel_notes/release_17_11.html#id4
https://doc.dpdk.org/
As outlined in the SRU template this is covered by the MRE verification
- setting this bug to verified (gating will be done by the MRE checks)
** Tags removed: verification-needed verification-needed-bionic
verification-needed-cosmic
** Tags added: verification-done verification-done-bionic
veri
Hello Talat, or anyone else affected,
Accepted dpdk into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/dpdk/17.11.5-0~ubuntu18.04.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:/
Hello Talat, or anyone else affected,
Accepted dpdk into cosmic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/dpdk/17.11.5-0~ubuntu18.10.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:/
FYI - all prechecks complete - uploaded to -unapproved
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799397
Title:
[dpdk]rte_memcpy() moves data incorrectly on Ubuntu 18.04 onIntel
Skylake.
** Description changed:
+ [Impact]
+
+ * Crashing on certain SkyLake Chips
+
+ * Follow upstream disabling one of the gcc options
+
+ [Test Case]
+
+ * Part of the MRE bug 1817675 following the MRE verficiation process as
+defined there.
+
+ [Regression Potential]
+
+ * Rebuilds wit
17.11.5 carries
http://git.dpdk.org/dpdk-stable/commit/?id=1bc8541000ff27f2ff4da3349b90cc2fd650523f
So this shall be fixed in the upcoming MRE update.
** Changed in: dpdk
Status: New => Fix Released
** Changed in: gcc-7 (Ubuntu)
Status: New => Invalid
** Also affects: dpdk (Ubuntu
The compilers didn't make a difference.
The versions in Disco for gcc7/8 generate the same results.
But then for me it never generated the wrong code:
Steps:
git clone git://dpdk.org/dpdk
apt build-dep dpdk
apt install gdb build-essential libmnl-dev
apt update && apt upgrade
make defconfig
vim b
PPA to test newer gcc versions in Bionic
=> https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3514/+packages
But debugging turned out I seem to really need an affected machine to get any
further :-/
I'll ask around if one could hand me a login.
--
You received this bug notification be
Suspicious sequence is in most, functions reported to be broken - but it
is not identical to what is reported upstream:
(bionic-amd64)root@Keschdeichel:/build/dpdk-9ZbA0X/dpdk-18.08# gdb -batch -ex
'file /tmp/testpmd-skylakeavx512' -ex 'set disassembly-flavor intel' -ex
'disassemble/rs mlx5_tx_b
I checked the default build, as expected no breakage.
But this no more is about the default dpdk build, but a potential gcc bug lets
ignore the default gcc build and use DPDK source as a test.
To enable a non portable build you would have to use the rte_machine
DBE_BUILD_OPTION in dpdk.
$ DEB_BU
Upstream bug is at https://bugs.dpdk.org/show_bug.cgi?id=97#c18
(Can't link it here :-/ )
They say:
- No crash seen with code generated by clang-6 or gcc-6, probably because they
do not generate AVX512 instructions.
- Crash is confirmed with gcc-7 and gcc-8 when using AVX2 version of rte_memcpy.
is that seen as well with gcc-7 in disco, or gcc-8 in disco?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799397
Title:
[dpdk]rte_memcpy() moves data incorrectly on Ubuntu 18.04 onIntel
Skyl
copy&paste interim summary from upstream thread
Summary:
- CPU: Intel Skylake
- Linux environment: Ubuntu 18.04
- Compiler: GCC 7 or 8
- Scenario: testpmd crashes when it starts forwarding
- Behaviour: AVX2 version of rte_memcpy() fails if optimized for AVX5
It seems offsets are compiled wrong with our compiler
Being a potential gcc bug I'll subscribe doko and add a bug task.
--- bad-avx512-enabled
+++ good-avx512-disabled
-vmovdqu8 xmm0,XMMWORD PTR [rax*8+0x0]
+vmovdqu xmm0,XMMWORD PTR [rax*8+0x0]
vinserti128 ymm0,ymm0,XMMWORD PTR [rax
In the upstream discussion my confusion was resolved, this is in fact no issue
of the binaries we generate.
It only happens if you rebuild it yourself with AVX512f enabled.
I'll participate and track the upstream discussion in case we can help fixing
the code anyway - but by the provided binaries
See discussions at and around
http://mails.dpdk.org/archives/dev/2018-November/118121.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799397
Title:
[dpdk]rte_memcpy() moves data incorrectly on U
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: dpdk (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799397
Title:
[dpdk
19 matches
Mail list logo
