Bug ID 780809: Invalid memory address encountered by virtualized-interface xnet driver

Last Modified: Apr 11, 2024

Affected Product(s):
BIG-IP MA-VE(all modules)

Known Affected Versions:
14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 15.0.0, 15.0.1, 15.0.1.1, 15.1.0, 15.1.0.1

Fixed In:
16.0.0, 15.1.0.2, 15.0.1.2, 14.1.2.3

Opened: May 08, 2019

Severity: 3-Major

Symptoms

Tmm crashes with the following in /var/log/ltm: -- notice /sys/bus/pci/devices/0000:00:06.0/driver/unbind: No such file or directory. -- notice xnet_lib Error[0:6.0]: Failed to unbind igb_uio driver.

Impact

Traffic disrupted while tmm restarts.

Conditions

BIG-IP Virtual Edition or Cloud Edition configured to use the DPDK-derived 'xnet' device driver for the network interface.

Workaround

It is possible to prevent the TMM panic by substituting the 'sock' device driver for the 'xnet' driver. This must be manually configured by creating a special configuration file, 'tmm_init.tcl'. As soon as possible after the BIG-IP instance has begun to reboot, when the bash shell can be accessed, carefully enter these commands: # echo "device driver vendor_dev 1d0f:ec20 sock" >> /config/tmm_init.tcl # echo "ndal force_sw_tcs off 1d0f:ec20" >> /config/tmm_init.tcl Then confirm that the file contains the expected contents: # cat /config/tmm_init.tcl Then restart the TMM: # bigstart restart tmm

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips