Last Modified: Oct 16, 2025
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
17.1.1.1, 17.1.1.2, 17.1.1.3, 17.1.1.4, 17.1.2, 17.1.2.1, 17.1.2.2, 17.1.3, 17.5.0, 17.5.1, 17.5.1.2, 17.5.1.3
Opened: Aug 20, 2025 Severity: 3-Major
TMM in restart loop with 'tmm' logging saying that failed to initialize xnet driver <13> Aug 12 05:21:05 localhost.localdomain notice xnet_dev [0000:00:0c.0]: Kernel driver is already unbound or no such device <13> Aug 12 05:21:14 localhost.localdomain notice xnet_lib [pci:0000:00:0c.0]: Error: Failed to initialize driver <13> Aug 12 05:21:14 localhost.localdomain notice xnet_dev [0000:00:0c.0]: Kernel driver is already unbound or no such device <13> Aug 12 05:21:14 localhost.localdomain notice xnet_dev [0000:00:0c.0]: Error: Unsuccesful bind operation <13> Aug 12 05:21:14 localhost.localdomain notice xnet[00:0c.0]: Error: Unable to attach to xnet dev <13> Aug 12 05:21:14 localhost.localdomain notice xnet(1.3)[00:0c.0]: Error: Unable to initialize device <13> Aug 12 05:21:14 localhost.localdomain notice xnet(1.3)[00:0c.0]: Waiting for tmm1 to reach state 4... <13> Aug 12 05:21:14 localhost.localdomain notice ndal Error: Restarting TMM <13> Aug 12 05:21:14 localhost.localdomain notice Initiating TMM shutdown. <13> Aug 12 05:21:14 localhost.localdomain notice tap(tap)[00:00.0]: Waiting for tmm1 to reach state 4... <13> Aug 12 05:21:20 localhost.localdomain notice --------------------------------------------- Logging about receiving an unexpected message from PF may also be observed in 'tmm' log: <13> Aug 12 05:19:56 localhost.localdomain notice iavf[0000:00:0a.0]: Received unexpected message 0 from PF
Traffic disrupted as TMM never comes up
1) xnet-IAVF driver 2) TMM crashes or restarts after issuing multiple 'modprobe -r i40evf' commands within a short time (<30 seconds)
Restart VM host to reset the PF
None