QAT unable to attach on C2358 23.05-BETA
-
I have an old FW-7551B-NG1 unit I'm using for testing and lab stuff. I just wiped and reinstalled pfSense+ on it and decided to give the new 23.05 beta a try. I noticed that now QAT refuses to attach - on the dashboard widget it shows "QAT Crypto: Yes (inactive)" despite its selection in the advanced settings. I toggled IPsec-MB crypto on and off to test, and that doesn't seem to affect it.
A quick "sysctl -a | grep qat" shows:
qat_ocf0: <QAT engine> qat_ocf0: no QAT IRQ instances available device_attach: qat_ocf0 attach returned 6 dev.qat_ocf.%parent:Any ideas?
-
Almost certainly because the module is missing in beta. It will be there in the RC when that goes public though:
[23.05-RC][admin@4860.stevew.lan]/root: ls -ls /boot/kernel/qat_c2* 69 -r-xr-xr-x 1 root wheel 123256 May 4 19:15 /boot/kernel/qat_c2xxx.ko 157 -r-xr-xr-x 1 root wheel 276928 May 4 19:15 /boot/kernel/qat_c2xxxfw.koSteve
-
@stephenw10 That makes sense, thanks! I checked and basically all the qat modules were there except the c2xxx ones. Not a blocking issue for me and if it were it'd be my fault for installing a beta on day 1 :) Thanks for clearing that up!
-
On the current RC snap we're testing I still see those errors but it does work:
qat_ocf0: <QAT engine> qat_ocf0: no QAT IRQ instances available device_attach: qat_ocf0 attach returned 6 qat_c2xxx0: <Intel C2000 QuickAssist PF> mem 0xdfe80000-0xdfe9ffff,0xdff30000-0xdff33fff at device 11.0 on pci0: vmstat -i | grep qat irq38: qat_c2xxx0 10008 6 -
@jimp Thanks - I'll wait for the RC and update this thread if the behavior doesn't clear.
-
@jimp Just installed yesterday's snapshot and all is well. Thanks!
