The NIC in the affected machine in Lexington has the following driver and firmware details:
$ ethtool -i eth4 driver: bnx2x version: 1.78.17-0 firmware-version: bc 7.10.4 phy 1.34 bus-info: 0000:06:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes
The following has been reported on another off-site system showing the same symptoms:
$ ethtool -i eth2 driver: bnx2x version: 1.78.17-0 firmware-version: bc 7.8.79 bus-info: 0000:01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes
The NIC in the affected machine in Lexington has the following driver and firmware details:
$ ethtool -i eth4 statistics: yes eeprom- access: yes register- dump: yes priv-flags: yes
driver: bnx2x
version: 1.78.17-0
firmware-version: bc 7.10.4 phy 1.34
bus-info: 0000:06:00.0
supports-
supports-test: yes
supports-
supports-
supports-
The following has been reported on another off-site system showing the same symptoms:
$ ethtool -i eth2 statistics: yes eeprom- access: yes register- dump: yes priv-flags: yes
driver: bnx2x
version: 1.78.17-0
firmware-version: bc 7.8.79
bus-info: 0000:01:00.0
supports-
supports-test: yes
supports-
supports-
supports-