From: Przemek Kitszel <przemyslaw.kitszel@intel.com>
To: Nebojsa Stevanovic <nebojsa.stevanovic@gcore.com>,
"jesse.brandeburg@intel.com" <jesse.brandeburg@intel.com>,
"anthony.l.nguyen@intel.com" <anthony.l.nguyen@intel.com>
Cc: "intel-wired-lan@lists.osuosl.org" <intel-wired-lan@lists.osuosl.org>
Subject: Re: [Intel-wired-lan] Bug report: Intel ICE driver
Date: Thu, 6 Jul 2023 13:18:46 +0200 [thread overview]
Message-ID: <01ff6c19-aa04-857e-ad62-cd2171661281@intel.com> (raw)
In-Reply-To: <VI1PR02MB439744DEDAA7B59B9A2833FE912EA@VI1PR02MB4397.eurprd02.prod.outlook.com>
On 7/4/23 10:50, Nebojsa Stevanovic wrote:
> Dear maintainers,
>
> We are experiencing issues with RX/TX counters on Intel NIC's using ICE
> driver.
> We started experiencing issues from kernel 6.2 onwards (6.3.5 also). We
> use vanilla kernel on Ubuntu 22.04 servers.
Thank you for the report, I will take a look, we will also try to
reproduce it locally.
>
> I've attached two screenshots of grafana dashboard - one showing metrics
> collected from firmware using ethtool, another collected from kernel
> (netlink or /proc/net/dev). As you can see, there are spikes showing
> over 400Tb/s received. We tried collecting metrics with different
> tools/scripts just to be sure that our collecting is not faulty, but the
> behaviour is same.
>
> Using proprietary drivers is not easy, since they are not up to date
> with the mainline kernel development and we are facing many issues
> during compilation.
>
> How to reproduce: Installing server with Ubuntu 22.04 and Intel NIC
> from E810 series. It happens more often on high traffic, but not exclusive.
>
> Please let me know if I can provide any more information.
Usually output of the `dmesg` command is attached for bug reports,
please make sure that you ran the command a moment after the bug pops up.
>
> Regards,
> Nebojša
> GCORE <https://gcorelabs.com/>
> *Nebojsa Stevanovic*
> Systems Engineer
> nebojsa.stevanovic@gcore.com <mailto:nebojsa.stevanovic@gcore.com>
> +381642677153 <tel:+381642677153>
> gcore.com <https://gcore.com/>
> <https://www.facebook.com/gcorelabscom/>
> <https://www.linkedin.com/company/g-core>
> <https://www.youtube.com/channel/UCFhtQE7HB097a1_Nfv-Ma_Q>
> <https://www.weibo.com/p/1005056986184457>
>
> This message is intended solely for the addressee and may contain
> confidential information. If you have received this message in error,
> please send it back to us, and immediately and permanently delete it. Do
> not use, copy or disclose the information contained in this message or
> in any attachment.
>
>
> _______________________________________________
> Intel-wired-lan mailing list
> Intel-wired-lan@osuosl.org
> https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
Thanks,
Przemek
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
prev parent reply other threads:[~2023-07-06 11:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <efa5aab9-3f11-44d0-a6ff-fe60099a3fed.673e22aa-1b68-4a30-b3cd-5f214452578c.345b7c07-92f3-48c3-aca7-e9991e5422a2@emailsignatures365.codetwo.com>
2023-07-04 8:50 ` [Intel-wired-lan] Bug report: Intel ICE driver Nebojsa Stevanovic
2023-07-06 11:18 ` Przemek Kitszel [this message]
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=01ff6c19-aa04-857e-ad62-cd2171661281@intel.com \
--to=przemyslaw.kitszel@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=nebojsa.stevanovic@gcore.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