# BlueField CQE Vender Syndrome Code 0x9f During Flow Hash Table Update **URL:** \ **Category:** BlueField\ **Created:** [January 16, 2026, 3:04am UTC](https://forums.developer.nvidia.com/t/bluefield-cqe-vender-syndrome-code-0x9f-during-flow-hash-table-update/357731 "2026-01-16T03:04:48Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![pusnow1](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@pusnow1](https://forums.developer.nvidia.com/u/pusnow1)\ **Post date:** [January 16, 2026, 3:04am UTC](https://forums.developer.nvidia.com/t/bluefield-cqe-vender-syndrome-code-0x9f-during-flow-hash-table-update/357731/1 "2026-01-16T03:04:48Z")
Hi, During updating flow hash table through WQE, I’ve encountered a CQE Error whose syndrome and vendor\_err\_synd are syndrome: 0x2 vendor\_err\_synd: 0x9f Could you please provide the meaning and recommended actions for this error? ---
**Author:** ![xyin](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@xyin](https://forums.developer.nvidia.com/u/xyin)\ **Post date:** [January 20, 2026, 3:13am UTC](https://forums.developer.nvidia.com/t/bluefield-cqe-vender-syndrome-code-0x9f-during-flow-hash-table-update/357731/2 "2026-01-20T03:13:33Z")
Hi Pusnow1 We’ll probably need a bit more context before we can narrow down the issue. Could you please share a few more details? - The full error message / log line that includes this CQE error (with the `syndrome`, `vendor_err_synd`) - The exact DOCA / SDK version you’re using - BlueField NIC firmware version (output of `mlxfwmanager -d q` or `flint -d q`) - Which DOCA sample or application was running, and roughly what operation it was doing when the error occurred Thanks Xu ---
**Author:** ![pusnow1](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@pusnow1](https://forums.developer.nvidia.com/u/pusnow1)\ **Post date:** [January 20, 2026, 4:43pm UTC](https://forums.developer.nvidia.com/t/bluefield-cqe-vender-syndrome-code-0x9f-during-flow-hash-table-update/357731/3 "2026-01-20T16:43:04Z")
Hi Xu, 1. I’m currently directly issuing commands through DevX with PRM. so I only got CQE Error syndrome: 0x2 vendor\_err\_synd: 0x9f 1. upstream rdma-core library, but I’m only using DevX APIS (e.g., mlx5dv\_devx\_obj\_create) 2. Device Type: BlueField3 Part Number: 900-9D3B6-00CV-A\_Ax Description: NVIDIA BlueField-3 B3220 P-Series FHHL DPU; 200GbE (default mode) / NDR200 IB; Dual-port QSFP112; PCIe Gen5.0 x16 with x16 PCIe extension option; 16 Arm cores; 32GB on-board DDR; integrated BMC; Crypto Enabled PSID: MT\_0000000884 PCI Device Name: mlx5\_2 Base MAC: XXX Versions: Current Available FW 32.43.1014 N/A PXE 3.7.0500 N/A UEFI 14.36.0016 N/A UEFI Virtio blk 22.4.0014 N/A UEFI Virtio net 21.4.0013 N/A Status: No matching image found 1. No RDMA-Core / Doca / DPDK sample application covers my use cases 1. Flow Hash Table in RDMA-Core directly accesses ICM, not documented in PRM I have 2. Flow Hash Table in DPDK uses GTA WQE not documented in PRM I have 3. The Only Documented Flow Hash Table WQE in PRM I have is FlowUpdate WQE. Thanks, Wonsup ---
**Author:** ![xyin](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@xyin](https://forums.developer.nvidia.com/u/xyin)\ **Post date:** [January 21, 2026, 1:49am UTC](https://forums.developer.nvidia.com/t/bluefield-cqe-vender-syndrome-code-0x9f-during-flow-hash-table-update/357731/4 "2026-01-21T01:49:06Z")
Hi Wonsup, Thanks for the update. Short answer on the CQE: - `syndrome = 0x2` is a Local QP Operation Error – the HCA is unhappy with the WQE or local resources (QP/context/memory), not with the remote side or the wire. - `vendor_err_synd = 0x9f` is a device‑specific extension code. It isn’t decoded in the PRM version you have. Internally, this kind of combo (0x2 + a vendor code) usually shows up when the operation or resources are considered invalid or unsupported – e.g. WQE format not what the HCA expects, a feature/capability not enabled, or an access that doesn’t line up with the configured memory / ICM layout. In your setup, you are: - Using upstream rdma-core, but only the DevX APIs (e.g. `mlx5dv_devx_obj_create`), and - Implementing flow hash table updates directly based on PRM, while noting that: Given this, the most likely interpretation is: - The CQE error is not indicating a generic link/transport issue, but rather that the specific WQE / flow‑hash‑table update path you are using is outside the set of documented and supported interfaces in your PRM revision, so the device rejects the operation and reports a local‑operation error with a vendor‑specific syndrome. Practically, I may suggest you: - Limit your DevX usage for flow programming to documented WQE types and commands in the PRM you have (e.g. the documented FlowUpdate WQE), or to higher‑level APIs in DOCA / DPDK / rdma-core that are explicitly supported for flow programming. - Avoid relying on: With the current undocumented path, there is no official programming model we can rely on to give a precise “do X to fix 0x9f” instruction. Regards Xu ---
**Author:** ![pusnow1](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@pusnow1](https://forums.developer.nvidia.com/u/pusnow1)\ **Post date:** [January 21, 2026, 2:13am UTC](https://forums.developer.nvidia.com/t/bluefield-cqe-vender-syndrome-code-0x9f-during-flow-hash-table-update/357731/5 "2026-01-21T02:13:28Z")
Hi Xu, Thank you for your kind answer and suggestions! I will stick into rdma-core’s higer level APIs. Thanks, Wonsup ---
**Author:** ![system](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/system/32/68080_2.png) [@system](https://forums.developer.nvidia.com/u/system)\ **Post date:** [February 4, 2026, 2:13am UTC](https://forums.developer.nvidia.com/t/bluefield-cqe-vender-syndrome-code-0x9f-during-flow-hash-table-update/357731/6 "2026-02-04T02:13:33Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.