pfSense » pfSense Plus

If the QAT module is loaded but the driver did not attached to the hardware, the dashboard still reports "QAT: Yes (active)" when it is in fact not active.

For example on C2K systems where the qat_c2xxx module wasn't loaded, the other modules were there but there was no qatX device, pciconf still reported it as noneX.

: pciconf -l -l
[...]
none0@pci0:0:11:0:      0b4000   02   00   8086   1f18   8086   0000
[...]
: kldstat
[...]
 7    1 0xffffffff8472a000     4348 qat.ko
 8    5 0xffffffff8472f000    10e10 qat_hw.ko
 9    7 0xffffffff84740000    29840 qat_common.ko
10    6 0xffffffff8476a000    66b78 qat_api.ko
[...]

Load the right module and then it's properly activated:

: kldload qat_c2xxx
qat_c2xxx0: <Intel C2000 QuickAssist PF> mem 0xdfe80000-0xdfe9ffff,0xdff30000-0xdff33fff at device 11.0 on pci0
: pciconf -l -l
[...]
qat_c2xxx0@pci0:0:11:0: 0b4000   02   00   8086   1f18   8086   0000
[...]
: kldstat
Id Refs Address                Size Name
 7    1 0xffffffff8472a000     4348 qat.ko
 8    5 0xffffffff8472f000    10e10 qat_hw.ko
 9    7 0xffffffff84740000    29840 qat_common.ko
10    6 0xffffffff8476a000    66b78 qat_api.ko
13    1 0xffffffff847e8000    11240 qat_c2xxx.ko

It's rare that we would have listed a QAT device ID as being known but the card isn't supported by the drivers, but still possible.

This specific C2K case is being handled elsewhere to ensure the modules are loaded, but it's still best to ensure this output is accurate in case of other failures.

To me, I have a working fix to commit shortly.