intel-wired-lan.lists.osuosl.org archive mirror
 help / color / mirror / Atom feed
From: Nebojsa Stevanovic <nebojsa.stevanovic@gcore.com>
To: "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: [Intel-wired-lan] Bug report: Intel ICE driver
Date: Tue, 4 Jul 2023 08:50:46 +0000	[thread overview]
Message-ID: <VI1PR02MB439744DEDAA7B59B9A2833FE912EA@VI1PR02MB4397.eurprd02.prod.outlook.com> (raw)
In-Reply-To: efa5aab9-3f11-44d0-a6ff-fe60099a3fed.673e22aa-1b68-4a30-b3cd-5f214452578c.345b7c07-92f3-48c3-aca7-e9991e5422a2@emailsignatures365.codetwo.com


[-- Attachment #1.1: Type: text/plain, Size: 1914 bytes --]

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.

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.

Regards,
Nebojša
[https://my.gcdn.co/images/web_3253/logo_g.png]<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://my.gcdn.co/images/web_3253/face.png]<https://www.facebook.com/gcorelabscom/>   [https://my.gcdn.co/images/web_3253/in.png] <https://www.linkedin.com/company/g-core>   [https://my.gcdn.co/images/web_3253/yout.png] <https://www.youtube.com/channel/UCFhtQE7HB097a1_Nfv-Ma_Q>        [https://my.gcdn.co/images/web_3253/weib.png] <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.

[-- Attachment #1.2: Type: text/html, Size: 10025 bytes --]

[-- Attachment #2: ethtool_scrape.png --]
[-- Type: image/png, Size: 123259 bytes --]

[-- Attachment #3: kernel_driver_scrape.png --]
[-- Type: image/png, Size: 147674 bytes --]

[-- Attachment #4: Type: text/plain, Size: 162 bytes --]

_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan

       reply	other threads:[~2023-07-05 15:14 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 ` Nebojsa Stevanovic [this message]
2023-07-06 11:18   ` [Intel-wired-lan] Bug report: Intel ICE driver Przemek Kitszel

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=VI1PR02MB439744DEDAA7B59B9A2833FE912EA@VI1PR02MB4397.eurprd02.prod.outlook.com \
    --to=nebojsa.stevanovic@gcore.com \
    --cc=anthony.l.nguyen@intel.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jesse.brandeburg@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).