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.

Description of problem:
It has been noticed that "ethtool -e <device>" for several types of NICs negatively affects the underlying system. In particular:

- bz1869724: RHEL8.3, bnx2x driver, the device is paused for several seconds
- bz1917074: RHEL7.*, tg3 driver (maybe in ovs-dpdk bond only), OOM / memory balloon, command hung, ports flapped
- bz1917196: RHEL8.*, i40e driver, network glitch for 17 seconds

We don't claim the three bugzillas have the same root cause, as they were noticed on different driver types. But all were noticed in quite short timeframe, so *probably* they can have something in common.

Please make the eeprom dump ore robust, not affecting production.


Version-Release number of selected component (if applicable):
See above BZs for details.


How reproducible:
100% per the reproducers in the three BZs.


Steps to Reproduce:
1. See the BZs.


Actual results:
eeprom dump negatively affects the network traffic for too long time


Expected results:
No impact to production (I guess a very short delay can be acceptable).


Additional info:

closing it in favour of driver specific BZs:

tg3 - https://bugzilla.redhat.com/show_bug.cgi?id=1918875
i40e - https://bugzilla.redhat.com/show_bug.cgi?id=1918889
bnx2x - https://bugzilla.redhat.com/show_bug.cgi?id=1918897

*** This bug has been marked as a duplicate of bug 1918875 ***