(In reply to nacurry from comment #0)
> Steps to Reproduce:
> 1. Set up ovs-dpdk on intel x710s
>    - (maybe) needs to be balance-tcp
>    - (maybe) needs to have userspace and kernel driver loaded on same card
> without enabling support-multi-driver


So the request is to stop collecting "ethtool -e" in that setup, am I right? We can predicate calling the command, but could you please provide a diagnostic command to determine such setup?

(an example: similar issues happen on bnx2x NICs; so when "ethtool -i %DEV" contains "bnx2x" string, we skip calling "ethtool -e %DEV" [1];  please provide similar command/condition)

[1] https://github.com/sosreport/sos/pull/2200/files

"ethtool -i %DEV" contains "tg3" string

should be enough to match network cards that are seeing this issue with sos

Upstream PR proposed.

Leaving on jjansky to decide about inclusion in RHEL7. In RHEL8, it should be contained in 8.5 by default. If sooner fix is required, let clone the BZ to RHEL8 (but I dont want to promise anything..).

We are looking at getting an erratum pushed out for this asap that will alleviate the reported issue and prevent the default running of ethtool -e.
Additional investigation will also be needed to determine why the this long standing diagnostic tool has recently become disruptive to certain environments.

I tested this manually by wrapping ethtool binary file on RHEL-7.9 x86_64

SETUP

# cat /root/fakebin/ethtool
#!/bin/bash

# /usr/sbin/original-ethtool $@ | sed 's/driver: .*/driver: bnx2x/'
/usr/sbin/original-ethtool ethtool $@ | sed 's/driver: .*/driver: tg3/' 

# chmod u+x /root/fakebin/ethtool
# mv /usr/sbin/ethtool /usr/sbin/original-ethtool
# ln -s /root/fakebin/ethtool /usr/sbin/ethtool


+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

OLD
# rpm -qa sos
sos-3.9-5.el7_9.1.noarch

# sosreport --list-plugins | grep 'networking\.'
 networking.traceroute     off             collect a traceroute to www.example.com
 networking.namespace_pattern                 Specific namespaces pattern to be collected, namespaces pattern should be separated by whitespace as for example "eth* ens2"
 networking.namespaces     0               Number of namespaces to collect, 0 for unlimited. Incompatible with the namespace_pattern plugin option
 networking.ethtool_namespaces on              Define if ethtool commands should be collected for namespaces

With bnx2x driver
# sosreport -o networking --batch
...
[plugin:networking] skipped command 'ethtool -e eth0': 
...
Your sosreport has been generated and saved in:
  /var/tmp/sosreport-localhost-2021-01-25-dzeixss.tar.xz


With tg3 driver
# sosreport -o networking --batch
...
Your sosreport has been generated and saved in:
  /var/tmp/sosreport-localhost-2021-01-25-ixtpwuf.tar.xz

# tar tf /var/tmp/sosreport-localhost-2021-01-25-ixtpwuf.tar.xz| grep ethtool_-e
sosreport-localhost-2021-01-25-ixtpwuf/sos_commands/networking/ethtool_-e_eth0
sosreport-localhost-2021-01-25-ixtpwuf/sos_commands/networking/ethtool_-e_lo

+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

NEW

# rpm -qa sos
sos-3.9-5.el7_9.noarch

We can see that eepromdump is now ignored by default
# sosreport --list-plugins | grep 'networking\.'
 networking.traceroute     off             collect a traceroute to www.example.com
 networking.namespace_pattern                 Specific namespaces pattern to be collected, namespaces pattern should be separated by whitespace as for example "eth* ens2"
 networking.namespaces     0               Number of namespaces to collect, 0 for unlimited. Incompatible with the namespace_pattern plugin option
 networking.ethtool_namespaces on              Define if ethtool commands should be collected for namespaces
 networking.eepromdump     off             collect 'ethtool -e' for all devices 


With bnx2x driver
# sosreport -o networking --batch
...
Your sosreport has been generated and saved in:
  /var/tmp/sosreport-localhost-2021-01-25-qmqodau.tar.xz

# tar tf /var/tmp/sosreport-localhost-2021-01-25-qmqodau.tar.xz | grep ethtool_-e

With tg3 driver
# sosreport -o networking --batch
...
Your sosreport has been generated and saved in:
  /var/tmp/sosreport-localhost-2021-01-25-jwqopke.tar.xz

# tar tf /var/tmp/sosreport-localhost-2021-01-25-jwqopke.tar.xz| grep ethtool_-e

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (sos bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2021:0333