patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
To: Abhishek Marathe <Abhishek.Marathe@microsoft.com>
Cc: Kevin Traynor <ktraynor@redhat.com>,
	Ju-Hyoung Lee <juhlee@microsoft.com>,
	 "stable@dpdk.org" <stable@dpdk.org>,
	"dev@dpdk.org" <dev@dpdk.org>, Akhil Goyal <akhil.goyal@nxp.com>,
	Ali Alnubani <alialnu@mellanox.com>,
	 "benjamin.walker@intel.com" <benjamin.walker@intel.com>,
	David Christensen <drc@linux.vnet.ibm.com>,
	 Hemant Agrawal <hemant.agrawal@nxp.com>,
	Ian Stokes <ian.stokes@intel.com>,
	 Jerin Jacob <jerinj@marvell.com>,
	John McNamara <john.mcnamara@intel.com>,
	 Luca Boccassi <bluca@debian.org>, Pei Zhang <pezhang@redhat.com>,
	 "pingx.yu@intel.com" <pingx.yu@intel.com>,
	"qian.q.xu@intel.com" <qian.q.xu@intel.com>,
	 Raslan Darawsheh <rasland@mellanox.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	"yuan.peng@intel.com" <yuan.peng@intel.com>,
	"zhaoyan.chen@intel.com" <zhaoyan.chen@intel.com>
Subject: Re: [dpdk-stable] [dpdk-dev] 18.11.3 (LTS) patches review and test
Date: Thu, 17 Oct 2019 15:54:57 +0200	[thread overview]
Message-ID: <CAATJJ0KpQqc+wECHAx+CaarCM_t1KPQtQjdMxEWSwdcEw2on5g@mail.gmail.com> (raw)
In-Reply-To: <MWHPR21MB08320D805128058C0BC742279E930@MWHPR21MB0832.namprd21.prod.outlook.com>

Azure image: 'Canonical UbuntuServer 18.04-DAILY-LTS latest':
>
> * PERF-DPDK-SINGLE-CORE-PPS-DS4: FAILED
> * VERIFY-DPDK-OVS: PASSED
> * VERIFY-DPDK-BUILD-AND-TESTPMD-TEST: PASSED
> * VERIFY-SRIOV-FAILSAFE-FOR-DPDK: PASSED
> * PERF-DPDK-MULTICORE-PPS-F32: FAILED

Hi Abhishek,
since you use the daily LTS image and see such a significant change
compared to before, could it by any chance be that this made you
switch from kernel 4.15 to 5.0.
Because by the normal HWE policy [1] this got into Bionic rebuilds and
it seems [2] the same is true for linux-azure kernel flavours.

Could you check your logs if the kernel version changed between the
old and the new runs?
An alternative might be to rerun 18.11.2 to see if it drops as well,
which might indicate that it wasn't 18.11.2 -> 18.11.3 but something
else like the kernel.

Not sure if that old kernel is ok, but you always can go back to what
a version was released with. So in this case
package linux-azure=4.15.0.1009.9 is still there and you could try
18.11.3 with that maybe?

Let me know if you need help changing kernels there.

[1]: https://wiki.ubuntu.com/Kernel/LTSEnablementStack
[2]: https://launchpad.net/ubuntu/+source/linux-azure/+publishinghistory

  parent reply	other threads:[~2019-10-17 13:55 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-13 16:31 [dpdk-stable] " Kevin Traynor
2019-09-19 10:22 ` Yu, PingX
2019-09-19 21:33   ` Ju-Hyoung Lee
2019-09-19 22:44     ` Abhishek Marathe
2019-09-23 16:18       ` Kevin Traynor
2019-09-25 16:06   ` Kevin Traynor
2019-09-26  7:41     ` Yu, PingX
2019-10-03 13:30       ` Kevin Traynor
2019-10-08 10:22         ` Yu, PingX
2019-10-11  9:39           ` Kevin Traynor
2019-10-03 13:20 ` Kevin Traynor
2019-10-11 16:29   ` Abhishek Marathe
2019-10-11 16:33     ` Ju-Hyoung Lee
2019-10-11 16:49       ` Luca Boccassi
2019-10-11 21:19       ` Kevin Traynor
2019-10-15 16:21         ` Kevin Traynor
2019-10-15 17:12           ` Abhishek Marathe
2019-10-15 17:19             ` Kevin Traynor
2019-10-22 10:52               ` [dpdk-stable] [dpdk-dev] " Kevin Traynor
2019-10-22 17:44                 ` Abhishek Marathe
2019-10-22 18:02                   ` Kevin Traynor
2019-10-17 13:54             ` Christian Ehrhardt [this message]
2019-10-20 13:16               ` Ali Alnubani
2019-10-21  8:54                 ` Kevin Traynor
2019-10-04  2:28 ` [dpdk-stable] " Pei Zhang
2019-10-04  9:37   ` Kevin Traynor
2019-10-07 20:01 ` [dpdk-stable] [dpdk-dev] " Thinh Tran
2019-10-07 20:11   ` Ju-Hyoung Lee
2019-10-11  9:34   ` Kevin Traynor
2019-10-10 18:39 ` [dpdk-stable] " Stokes, Ian
2019-10-11  9:41   ` Kevin Traynor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAATJJ0KpQqc+wECHAx+CaarCM_t1KPQtQjdMxEWSwdcEw2on5g@mail.gmail.com \
    --to=christian.ehrhardt@canonical.com \
    --cc=Abhishek.Marathe@microsoft.com \
    --cc=akhil.goyal@nxp.com \
    --cc=alialnu@mellanox.com \
    --cc=benjamin.walker@intel.com \
    --cc=bluca@debian.org \
    --cc=dev@dpdk.org \
    --cc=drc@linux.vnet.ibm.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=ian.stokes@intel.com \
    --cc=jerinj@marvell.com \
    --cc=john.mcnamara@intel.com \
    --cc=juhlee@microsoft.com \
    --cc=ktraynor@redhat.com \
    --cc=pezhang@redhat.com \
    --cc=pingx.yu@intel.com \
    --cc=qian.q.xu@intel.com \
    --cc=rasland@mellanox.com \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    --cc=yuan.peng@intel.com \
    --cc=zhaoyan.chen@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).