This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2094200 - e1000e painfully slow on I219-V NIC
Summary: e1000e painfully slow on I219-V NIC
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: kernel
Version: CentOS Stream
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Ken Cox
QA Contact: Dipali
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-06-07 06:03 UTC by George
Modified: 2023-09-21 20:07 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-21 20:07:15 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Slow Speed Test (23.84 KB, image/png)
2022-06-08 23:41 UTC, George 		no flags Details
Speed Test with googled fix (26.53 KB, image/png)
2022-06-08 23:42 UTC, George 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Linux Kernel 213377 0 P1 NEW Poor receive speeds using e1000e driver on Intel I219-V 2022-07-22 15:29:53 UTC
Red Hat Issue Tracker   RHEL-6720 0 None Migrated None 2023-09-21 20:07:08 UTC
Red Hat Issue Tracker RHELPLAN-124425 0 None None None 2022-06-07 06:09:42 UTC

Description George 2022-06-07 06:03:26 UTC 
Description of problem:
Intel e1000e NIC painfully slow
Version-Release number of selected component (if applicable):
driver: e1000e
version: 5.14.0-101.el9.x86_64
How reproducible:
Always

Steps to Reproduce:
1. Try yum update OR downlod binary from web
2.
3.

Actual results:
painfully slow

Expected results:
rapid downloads

Additional info:
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (13) I219-V (rev 20)

Only thing that helps so far is below but not convinced this is a complete solution
ethtool -C devicename rx-usecs 6000
Comment 1 George 2022-06-08 23:41:52 UTC 
Created attachment 1888168 [details]
Slow Speed Test
Comment 2 George 2022-06-08 23:42:47 UTC 
Created attachment 1888169 [details]
Speed Test with googled fix
Comment 3 George 2022-06-08 23:44:09 UTC 
Still an issue wih new kernel 5.14.0-105.
See attached speed tests.
Comment 4 George 2022-06-13 23:35:28 UTC 


     WITHOUT FIX

     rx_errors: 10558
     tx_errors: 0
     rx_length_errors: 0
     rx_over_errors: 0
     rx_crc_errors: 5279
     rx_frame_errors: 0
     rx_missed_errors: 0
     tx_aborted_errors: 0
     tx_carrier_errors: 0
     tx_fifo_errors: 0
     tx_heartbeat_errors: 0
     tx_window_errors: 0
     rx_long_length_errors: 0
     rx_short_length_errors: 0
     rx_align_errors: 0
     rx_csum_offload_errors: 0
     uncorr_ecc_errors: 0
     corr_ecc_errors: 0
     
    WITH FIX
    
     rx_errors: 6
     tx_errors: 0
     rx_length_errors: 0
     rx_over_errors: 0
     rx_crc_errors: 3
     rx_frame_errors: 0
     rx_missed_errors: 8632
     tx_aborted_errors: 0
     tx_carrier_errors: 0
     tx_fifo_errors: 0
     tx_heartbeat_errors: 0
     tx_window_errors: 0
     rx_long_length_errors: 0
     rx_short_length_errors: 0
     rx_align_errors: 0
     rx_csum_offload_errors: 0
     uncorr_ecc_errors: 0
     corr_ecc_errors: 0
Comment 5 George 2022-06-13 23:40:32 UTC 
Last error comparison was performed downloading the zoom linux x86_64 from the zoom download centre, about 121 MB.
Comment 6 Michal Schmidt 2022-07-22 15:29:53 UTC 
This looks similar: https://bugzilla.kernel.org/show_bug.cgi?id=213377
Comment 7 Ken Cox 2022-07-26 10:36:00 UTC 
(In reply to Michal Schmidt from comment #6)
> This looks similar: https://bugzilla.kernel.org/show_bug.cgi?id=213377

This does appear to be the same symptom.  If so, it should be fixed by upstream patch
  
        639e298f432f e1000e: Fix packet loss on Tiger Lake and later

This is included in the RHEL9.1 e1000e driver update which has not been merged yet.  It should be merged soon and be available in the nightly builds.
Comment 8 Michal Schmidt 2022-08-10 15:46:42 UTC 
kernel-5.14.0-142.el9 with the e1000e driver update is available now in CentOS Stream 9. Please test.
Comment 9 George 2022-08-10 23:57:13 UTC 
I can confirm that the new kernel has fixed my issues with e1000e download speeds.
In fact it appears to be a "complete" solution as I now have download speeds at about 1Gbps.
Thanks.
Comment 10 RHEL Program Management 2023-09-21 20:01:20 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 11 RHEL Program Management 2023-09-21 20:07:15 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.