Last Modified: Oct 17, 2023
Affected Product(s):
BIG-IP All
Known Affected Versions:
12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2, 12.1.0, 12.1.1, 12.1.2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 13.1.3.5, 13.1.3.6, 13.1.4, 13.1.4.1, 13.1.5, 13.1.5.1
Opened: Jun 26, 2015 Severity: 3-Major
When the IOMMU is enabled, the system may report crit tmm error messages due to a race condition that might occurs during start-up. Error messages appear in /var/log/ltm, similar to the following: crit tmm[14967]: 01010025:2: Device error: hsb interface 0 coalesce timed out. crit tmm[14967]: 01010025:2: Device error: hsb interface pde 0 access failed. crit tmm[14967]: 01230017:2: Unable to attach to PCI device 03:00.01 for Interface 0.1. ... crit tmm[14967]: 01010260:2: Hardware Error(Co-Processor): n3-crypto1 request queue stuck.
System remains INOPERATIVE and reports crit tmm error messages. Note: Although IOMMU is disabled by default, you can enable it using the BIOS utility, and newer platforms might enable it by default.
This may occur on startup as a result of a race condition between chmand and tmm with IOMMU enabled.
To recover from the INOPERATIVE state, disable IOMMU with the following command and restart the BIG-IP system: tmsh modify sys db kernel.iommu valued isable
None