Last Modified: Feb 13, 2019
See more info
Known Affected Versions:
11.4.1, 11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5
12.0.0, 11.6.0 HF6, 11.5.4, 11.4.1 HF9
Opened: Mar 24, 2015
Related AskF5 Article: K17473
TCP Segmentation Offload (TSO) packet initialization failure due to out-of-memory condition with the message: packet is locked by a driver.
TMM posts the assert message: packet is locked by a driver, then crashes.
This is related to tmm running out of memory while configured with TSO, on BIG-IP or VIPRION platforms which implement the HSB (High Speed Bridge) device in hardware. This problem may occur on all currently-supported BIG-IP or VIPRION platforms EXCEPT the following: BIG-IP 2000-/4000-series appliances. BIG-IP 1600, 3600 appliances.
Disable TSO (for more information, see SOL15609: Overview of TCP Segmentation Offload, available here: https://support.f5.com/kb/en-us/solutions/public/15000/600/sol15609.html): To enable or disable TSO functionality, you can use the following command syntax: tmsh modify sys db tm.tcpsegmentationoffload value <enable | disable> Note: After modifying the tm.tcpsegmentationoffload database variable, you must restart the TMM daemon by running the bigstart restart tmm command. Restarting TMM temporarily interrupts traffic processing. F5 recommends running this command only during a maintenance window.
TCP Segmentation Offload (TSO) packet is now cleared correctly with no packet-locked message.