From: Owen Hilyard <ohilyard@iol.unh.edu>
To: dev@dpdk.org, somnath.kotur@broadcom.com
Cc: "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 08:48:19 -0400 [thread overview]
Message-ID: <CAHx6DYBXb5pUt=S=Mc+iqx1tMqXeJ+-eB94DOw2NKbGgmdR7jg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 378 bytes --]
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
[-- Attachment #2: brcm_57414.zip --]
[-- Type: application/zip, Size: 48402 bytes --]
next reply other threads:[~2021-05-27 12:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-27 12:48 Owen Hilyard [this message]
2021-05-27 14:31 ` Somnath Kotur
-- 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='CAHx6DYBXb5pUt=S=Mc+iqx1tMqXeJ+-eB94DOw2NKbGgmdR7jg@mail.gmail.com' \
--to=ohilyard@iol.unh.edu \
--cc=ajit.khaparde@broadcom.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=somnath.kotur@broadcom.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).