All of lore.kernel.org
 help / color / mirror / Atom feed
From: Somnath Kotur <somnath.kotur@broadcom.com>
To: Owen Hilyard <ohilyard@iol.unh.edu>
Cc: dev <dev@dpdk.org>, "Yigit, Ferruh" <ferruh.yigit@intel.com>,
	 Ajit Khaparde <ajit.khaparde@broadcom.com>
Subject: Re: [dpdk-dev] [PATCH 2/2] net/bnxt: workaround for spurious zero counter values in Thor
Date: Thu, 27 May 2021 20:01:04 +0530	[thread overview]
Message-ID: <CAOBf=mu+0KV-w5hYm5NEc6nw-1E5+LKN80YyPa13L7RAZ3A-0A@mail.gmail.com> (raw)
In-Reply-To: <CAHx6DYBXb5pUt=S=Mc+iqx1tMqXeJ+-eB94DOw2NKbGgmdR7jg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 972 bytes --]

Hi Owen,
             Thank you for the heads up.  I still could not figure out how
to reproduce this though, i did not run into any issue on my end and i
tried launching testpmd with similar cmdline parameters as specified here
in the log(TestNicSingleCorePerf) , but no luck
In any case, looks like i'll have to respin a V2 to incorporate some
feedback , let's see if that runs into this issue again and if so , will
get in touch with you on how to proceed further for the repro

Thanks a lot
Som

On Thu, May 27, 2021 at 6:18 PM Owen Hilyard <ohilyard@iol.unh.edu> wrote:

> Sorry for breaking the thread, Gmail doesn't seem to let you reply to
> arbitrary message ids and I have the dpdk-dev list in batch mode.
>
> This patch series is consistently causing segfaults on the community lab
> Broadcom 25G system. This is a manual notification since the lab hasn't had
> scheduled the downtime to move to failure by default yet. I have attached
> the output.
>
> Owen
>

  reply	other threads:[~2021-05-27 14:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-27 12:48 [dpdk-dev] [PATCH 2/2] net/bnxt: workaround for spurious zero counter values in Thor Owen Hilyard
2021-05-27 14:31 ` Somnath Kotur [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-05-27  6:19 Somnath Kotur
2021-06-08 17:47 ` Ajit Khaparde
2021-06-08 17:55   ` Ajit Khaparde

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='CAOBf=mu+0KV-w5hYm5NEc6nw-1E5+LKN80YyPa13L7RAZ3A-0A@mail.gmail.com' \
    --to=somnath.kotur@broadcom.com \
    --cc=ajit.khaparde@broadcom.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=ohilyard@iol.unh.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.