Re: Alg errors with Intel QAT Card

[Neil Horman]

On Tue, Jun 13, 2017 at 01:32:55PM -0700, Raj Ammanur wrote:
> Hi Neil & Salvatore,
> 
> thanks for the replies. The soft reboot hasn't helped. I am trying a previous
> kernel version that works with a similar card that we installed in
> another server
> and that works fine. Will keep you posted.
> 
> Neil: have you found fix/workaround for the firmware errors or you just using
> a soft reboot? by that, you just mean unload and load the kernel modules or
> a system reboot. I have tried both.
> 
its the latter that works around the issue.  I belive a QAT firmware update will
be forthcomming to fix the issue

Neil

> thanks
> --Raj
> 
> On Tue, Jun 13, 2017 at 5:30 AM, Neil Horman  wrote:
> > On Mon, Jun 12, 2017 at 03:52:07PM +, Benedetto, Salvatore wrote:
> >> Hi Raj,
> >>
> >> I've compiled and tested kernel 4.12.0-rc4 and I can't reproduce your 
> >> issue.
> >> Are you seeing any of this with a previous kernel version? If not, git 
> >> bisect might
> >> help us finding the root-cause.
> >> Have you tried with another platform/hw?
> >>
> >> Regards,
> >> Salvatore
> >>
> > Try a soft reboot and see if the error clears up.  This looks a bit 
> > reminscient
> > of some firmware errors we've been chasing down
> > Neil
> >
> >> > -Original Message-
> >> > From: linux-crypto-ow...@vger.kernel.org [mailto:linux-crypto-
> >> > ow...@vger.kernel.org] On Behalf Of Raj Ammanur
> >> > Sent: Friday, June 9, 2017 7:37 PM
> >> > To: Linux Crypto Mailing List 
> >> > Subject: Alg errors with Intel QAT Card
> >> >
> >> > Hi
> >> >
> >> > I am seeing the below errors after  installing an Intel QAT card
> >> > and loading the upstreamed qat_dh895xcc and intel_qat modules.
> >> >
> >> > Have others seen similar errors and know if this is a known issue
> >> > and a fix exists or know whats going on ? This is with 4.12.0-rc4+
> >> > version of the kernel.
> >> >
> >> > Any help is sincerely appreciated.
> >> >
> >> > thanks
> >> > --Raj
> >> >
> >> >
> >> > [3.639046] dh895xcc :00:0b.0: qat_dev0 started 12 acceleration 
> >> > engines
> >> > [4.168887] alg: skcipher-ddst: Test 5 failed (invalid result) on
> >> > encryption for qat_aes_cbc
> >> > [4.217866] alg: skcipher-ddst: Chunk test 1 failed on encryption
> >> > at page 0 for qat_aes_ctr
> >> > [4.282042] alg: skcipher: Test 4 failed (invalid result) on
> >> > encryption for qat_aes_xts
> >> > [4.395210] alg: akcipher: test 1 failed for qat-rsa, err=-22
> >> > [root@dhcp-swlab-681 ~]# dmesg | grep -i alg
> >> > [1.499336] alg: No test for pkcs1pad(rsa,sha256)
> >> > (pkcs1pad(rsa-generic,sha256))
> >> > [2.562511] SELinux:  Class alg_socket not defined in policy.
> >> > [4.168887] alg: skcipher-ddst: Test 5 failed (invalid result) on
> >> > encryption for qat_aes_cbc
> >> > [4.217866] alg: skcipher-ddst: Chunk test 1 failed on encryption
> >> > at page 0 for qat_aes_ctr
> >> > [4.282042] alg: skcipher: Test 4 failed (invalid result) on
> >> > encryption for qat_aes_xts
> >> > [4.367682] alg: akcipher: encrypt test failed. Invalid output
> >> > [4.395210] alg: akcipher: test 1 failed for qat-rsa, err=-22
> >> > [4.431827] alg: dh: generate public key test failed. Invalid output
> >> > [4.431829] alg: dh: test failed on vector 1, err=-22
> >> >
> >> >
> >> > 83:00.0 Co-processor: Intel Corporation DH895XCC Series QAT
> >> > Subsystem: Intel Corporation Device 
> >> > Physical Slot: 2
> >> > Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> >> > Stepping- SERR+ FastB2B- DisINTx+
> >> > Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
> >> > SERR-  >> > Latency: 0, Cache Line Size: 32 bytes
> >> > Interrupt: pin A routed to IRQ 35
> >> > NUMA node: 1
> >> > Region 0: Memory at fb90 (64-bit, prefetchable) [size=512K]
> >> > Region 2: Memory at fbd4 (64-bit, non-prefetchable) [size=256K]
> >> > Region 4: Memory at fbd0 (64-bit, non-prefetchable) [size=256K]
> >> > Capabilities: [b0] MSI: Enable- Count=1/1 Maskable+ 64bit+
> >> > Address:   Data: 
> >> > Masking:   Pending: 
> >> > Capabilities: [60] MSI-X: Enable+ Count=33 Masked-
> >> > Vector table: BAR=2 offset=0003b000
> >> > PBA: BAR=2 offset=0003b800
> >> > Capabilities: [6c] Power Management version 3
> >> > Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-
> >> > ,D3cold-)
> >> > Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
> >> > Capabilities: [74] Express (v2) Endpoint, MSI 00
> >> > DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s <128ns, L1 <1us
> >> > ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset+ SlotPowerLimit 0.000W
> >> > DevCtl: Report errors: Correctable+ Non-Fatal+ Fatal+ Unsupported+
> >> > RlxdOrd- ExtTag+ PhantFunc- AuxPwr- NoSnoop+ FLReset-
> >> > MaxPayload 256 bytes, MaxReadReq 1024 bytes
> >> > DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr- 

Re: Alg errors with Intel QAT Card

[Raj Ammanur]

those previous alg error msgs are gone with 4.11.3-202.fc25.x86_64,
but now I see
multiple tracebacks like the ones below.

Looks like its been reported a few months back with 4.10.0-rc3+ , but
with no response
or further update:
https://www.spinics.net/lists/linux-crypto/msg23699.html


[  182.697358] WARNING: CPU: 6 PID: 558 at crypto/algapi.c:348
crypto_wait_for_test+0x60/0x80
[  182.699505] Modules linked in: ip6t_rpfilter ip6t_REJECT
nf_reject_ipv6 xt_conntrack ip_set nfnetlink ebtable_nat
ebtable_broute bridge st
p llc ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6
ip6table_raw ip6table_mangle ip6table_security iptable_nat
nf_conntrack_ipv4
nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack libcrc32c iptable_raw
iptable_mangle iptable_security ebtable_filter ebtables
ip6table_filter
ip6_tables crct10dif_pclmul ppdev qat_dh895xcc(+) crc32_pclmul
intel_qat ghash_clmulni_intel joydev parport_pc parport acpi_cpufreq
tpm_tis t
pm_tis_core tpm virtio_balloon qemu_fw_cfg i2c_piix4 dh_generic
authenc nfsd auth_rpcgss nfs_acl lockd grace sunrpc virtio_net
virtio_blk cir
rus drm_kms_helper ttm crc32c_intel drm serio_raw virtio_pci ixgbevf
virtio_ring virtio ata_generic pata_acpi
[  182.705805] CPU: 6 PID: 558 Comm: systemd-udevd Not tainted
4.11.3-202.fc25.x86_64 #1
[  182.706502] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996),
BIOS 1.9.1-1.fc24 04/01/2014
[  182.707269] Call Trace:
[  182.707513]  dump_stack+0x63/0x86
[  182.707825]  __warn+0xcb/0xf0
[  182.708098]  warn_slowpath_null+0x1d/0x20
[  182.708463]  crypto_wait_for_test+0x60/0x80
[  182.708842]  crypto_register_alg+0x5b/0x70
[  182.709208]  crypto_register_algs+0x3a/0x80
[  182.709599]  qat_algs_register+0x6c/0xc0 [intel_qat]
[  182.710041]  adf_dev_start+0xd1/0x160 [intel_qat]
[  182.710477]  adf_probe+0x5ec/0x610 [qat_dh895xcc]
[  182.710909]  local_pci_probe+0x45/0xa0
[  182.711250]  pci_device_probe+0xfa/0x150
[  182.711623]  driver_probe_device+0x2bb/0x460
[  182.712009]  __driver_attach+0xdf/0xf0
[  182.712349]  ? driver_probe_device+0x460/0x460
[  182.712751]  bus_for_each_dev+0x6c/0xc0
[  182.713099]  driver_attach+0x1e/0x20
[  182.713426]  bus_add_driver+0x170/0x270
[  182.713773]  driver_register+0x60/0xe0
[  182.714113]  ? 0xc01ba000
[  182.714425]  __pci_register_driver+0x4c/0x50
[  182.714811]  adfdrv_init+0x2f/0x1000 [qat_dh895xcc]
[  182.715255]  do_one_initcall+0x52/0x1a0
[  182.715618]  ? kmem_cache_alloc_trace+0x159/0x1b0
[  182.716047]  ? do_init_module+0x27/0x1f8
[  182.716406]  do_init_module+0x5f/0x1f8
[  182.716754]  load_module+0x27cc/0x2be0
[  182.717096]  SYSC_init_module+0x173/0x190
[  182.717461]  ? SYSC_init_module+0x173/0x190
[  182.717837]  SyS_init_module+0xe/0x10
[  182.718169]  do_syscall_64+0x67/0x180
[  182.719638]  entry_SYSCALL64_slow_path+0x25/0x25
[  182.721178] RIP: 0033:0x7fd22ee715ca
[  182.722622] RSP: 002b:7ffc498bc428 EFLAGS: 0246 ORIG_RAX:
00af
[  182.724415] RAX: ffda RBX: 55ba9680ca30 RCX: 7fd22ee715ca
[  182.726161] RDX: 7fd22f9a3995 RSI: 3f03 RDI: 55ba97066a00
[  182.727897] RBP: 7fd22f9a3995 R08: 55ba9680d460 R09: 
[  182.729624] R10:  R11: 0246 R12: 55ba97066a00
[  182.731326] R13: 55ba9681b030 R14: 0002 R15: 55ba9680ca30

On Tue, Jun 13, 2017 at 1:32 PM, Raj Ammanur  wrote:
> Hi Neil & Salvatore,
>
> thanks for the replies. The soft reboot hasn't helped. I am trying a previous
> kernel version that works with a similar card that we installed in
> another server
> and that works fine. Will keep you posted.
>
> Neil: have you found fix/workaround for the firmware errors or you just using
> a soft reboot? by that, you just mean unload and load the kernel modules or
> a system reboot. I have tried both.
>
> thanks
> --Raj
>
> On Tue, Jun 13, 2017 at 5:30 AM, Neil Horman  wrote:
>> On Mon, Jun 12, 2017 at 03:52:07PM +, Benedetto, Salvatore wrote:
>>> Hi Raj,
>>>
>>> I've compiled and tested kernel 4.12.0-rc4 and I can't reproduce your issue.
>>> Are you seeing any of this with a previous kernel version? If not, git 
>>> bisect might
>>> help us finding the root-cause.
>>> Have you tried with another platform/hw?
>>>
>>> Regards,
>>> Salvatore
>>>
>> Try a soft reboot and see if the error clears up.  This looks a bit 
>> reminscient
>> of some firmware errors we've been chasing down
>> Neil
>>
>>> > -Original Message-
>>> > From: linux-crypto-ow...@vger.kernel.org [mailto:linux-crypto-
>>> > ow...@vger.kernel.org] On Behalf Of Raj Ammanur
>>> > Sent: Friday, June 9, 2017 7:37 PM
>>> > To: Linux Crypto Mailing List 
>>> > Subject: Alg errors with Intel QAT Card
>>> >
>>> > Hi
>>> >
>>> > I am seeing the below errors after  installing an Intel QAT card
>>> > and loading the upstreamed qat_dh895xcc and intel_qat modules.
>>> >
>>> > Have others seen similar errors 

Re: Alg errors with Intel QAT Card

[Raj Ammanur]

Hi Neil & Salvatore,

thanks for the replies. The soft reboot hasn't helped. I am trying a previous
kernel version that works with a similar card that we installed in
another server
and that works fine. Will keep you posted.

Neil: have you found fix/workaround for the firmware errors or you just using
a soft reboot? by that, you just mean unload and load the kernel modules or
a system reboot. I have tried both.

thanks
--Raj

On Tue, Jun 13, 2017 at 5:30 AM, Neil Horman  wrote:
> On Mon, Jun 12, 2017 at 03:52:07PM +, Benedetto, Salvatore wrote:
>> Hi Raj,
>>
>> I've compiled and tested kernel 4.12.0-rc4 and I can't reproduce your issue.
>> Are you seeing any of this with a previous kernel version? If not, git 
>> bisect might
>> help us finding the root-cause.
>> Have you tried with another platform/hw?
>>
>> Regards,
>> Salvatore
>>
> Try a soft reboot and see if the error clears up.  This looks a bit 
> reminscient
> of some firmware errors we've been chasing down
> Neil
>
>> > -Original Message-
>> > From: linux-crypto-ow...@vger.kernel.org [mailto:linux-crypto-
>> > ow...@vger.kernel.org] On Behalf Of Raj Ammanur
>> > Sent: Friday, June 9, 2017 7:37 PM
>> > To: Linux Crypto Mailing List 
>> > Subject: Alg errors with Intel QAT Card
>> >
>> > Hi
>> >
>> > I am seeing the below errors after  installing an Intel QAT card
>> > and loading the upstreamed qat_dh895xcc and intel_qat modules.
>> >
>> > Have others seen similar errors and know if this is a known issue
>> > and a fix exists or know whats going on ? This is with 4.12.0-rc4+
>> > version of the kernel.
>> >
>> > Any help is sincerely appreciated.
>> >
>> > thanks
>> > --Raj
>> >
>> >
>> > [3.639046] dh895xcc :00:0b.0: qat_dev0 started 12 acceleration 
>> > engines
>> > [4.168887] alg: skcipher-ddst: Test 5 failed (invalid result) on
>> > encryption for qat_aes_cbc
>> > [4.217866] alg: skcipher-ddst: Chunk test 1 failed on encryption
>> > at page 0 for qat_aes_ctr
>> > [4.282042] alg: skcipher: Test 4 failed (invalid result) on
>> > encryption for qat_aes_xts
>> > [4.395210] alg: akcipher: test 1 failed for qat-rsa, err=-22
>> > [root@dhcp-swlab-681 ~]# dmesg | grep -i alg
>> > [1.499336] alg: No test for pkcs1pad(rsa,sha256)
>> > (pkcs1pad(rsa-generic,sha256))
>> > [2.562511] SELinux:  Class alg_socket not defined in policy.
>> > [4.168887] alg: skcipher-ddst: Test 5 failed (invalid result) on
>> > encryption for qat_aes_cbc
>> > [4.217866] alg: skcipher-ddst: Chunk test 1 failed on encryption
>> > at page 0 for qat_aes_ctr
>> > [4.282042] alg: skcipher: Test 4 failed (invalid result) on
>> > encryption for qat_aes_xts
>> > [4.367682] alg: akcipher: encrypt test failed. Invalid output
>> > [4.395210] alg: akcipher: test 1 failed for qat-rsa, err=-22
>> > [4.431827] alg: dh: generate public key test failed. Invalid output
>> > [4.431829] alg: dh: test failed on vector 1, err=-22
>> >
>> >
>> > 83:00.0 Co-processor: Intel Corporation DH895XCC Series QAT
>> > Subsystem: Intel Corporation Device 
>> > Physical Slot: 2
>> > Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
>> > Stepping- SERR+ FastB2B- DisINTx+
>> > Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
>> > SERR- > > Latency: 0, Cache Line Size: 32 bytes
>> > Interrupt: pin A routed to IRQ 35
>> > NUMA node: 1
>> > Region 0: Memory at fb90 (64-bit, prefetchable) [size=512K]
>> > Region 2: Memory at fbd4 (64-bit, non-prefetchable) [size=256K]
>> > Region 4: Memory at fbd0 (64-bit, non-prefetchable) [size=256K]
>> > Capabilities: [b0] MSI: Enable- Count=1/1 Maskable+ 64bit+
>> > Address:   Data: 
>> > Masking:   Pending: 
>> > Capabilities: [60] MSI-X: Enable+ Count=33 Masked-
>> > Vector table: BAR=2 offset=0003b000
>> > PBA: BAR=2 offset=0003b800
>> > Capabilities: [6c] Power Management version 3
>> > Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-
>> > ,D3cold-)
>> > Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
>> > Capabilities: [74] Express (v2) Endpoint, MSI 00
>> > DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s <128ns, L1 <1us
>> > ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset+ SlotPowerLimit 0.000W
>> > DevCtl: Report errors: Correctable+ Non-Fatal+ Fatal+ Unsupported+
>> > RlxdOrd- ExtTag+ PhantFunc- AuxPwr- NoSnoop+ FLReset-
>> > MaxPayload 256 bytes, MaxReadReq 1024 bytes
>> > DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr- TransPend-
>> > LnkCap: Port #0, Speed 5GT/s, Width x16, ASPM L0s, Exit Latency L0s
>> > <512ns, L1 unlimited
>> > ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp-
>> > LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk-
>> > ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
>> > LnkSta: Speed 5GT/s, Width x16, TrErr- Train- SlotClk- DLActive-
>> > BWMgmt- ABWMgmt-
>> > DevCap2: Completion Timeout: Range B, 

Re: Alg errors with Intel QAT Card

[Neil Horman]

On Mon, Jun 12, 2017 at 03:52:07PM +, Benedetto, Salvatore wrote:
> Hi Raj,
> 
> I've compiled and tested kernel 4.12.0-rc4 and I can't reproduce your issue.
> Are you seeing any of this with a previous kernel version? If not, git bisect 
> might
> help us finding the root-cause.
> Have you tried with another platform/hw?
> 
> Regards,
> Salvatore
> 
Try a soft reboot and see if the error clears up.  This looks a bit reminscient
of some firmware errors we've been chasing down
Neil

> > -Original Message-
> > From: linux-crypto-ow...@vger.kernel.org [mailto:linux-crypto-
> > ow...@vger.kernel.org] On Behalf Of Raj Ammanur
> > Sent: Friday, June 9, 2017 7:37 PM
> > To: Linux Crypto Mailing List 
> > Subject: Alg errors with Intel QAT Card
> > 
> > Hi
> > 
> > I am seeing the below errors after  installing an Intel QAT card
> > and loading the upstreamed qat_dh895xcc and intel_qat modules.
> > 
> > Have others seen similar errors and know if this is a known issue
> > and a fix exists or know whats going on ? This is with 4.12.0-rc4+
> > version of the kernel.
> > 
> > Any help is sincerely appreciated.
> > 
> > thanks
> > --Raj
> > 
> > 
> > [3.639046] dh895xcc :00:0b.0: qat_dev0 started 12 acceleration 
> > engines
> > [4.168887] alg: skcipher-ddst: Test 5 failed (invalid result) on
> > encryption for qat_aes_cbc
> > [4.217866] alg: skcipher-ddst: Chunk test 1 failed on encryption
> > at page 0 for qat_aes_ctr
> > [4.282042] alg: skcipher: Test 4 failed (invalid result) on
> > encryption for qat_aes_xts
> > [4.395210] alg: akcipher: test 1 failed for qat-rsa, err=-22
> > [root@dhcp-swlab-681 ~]# dmesg | grep -i alg
> > [1.499336] alg: No test for pkcs1pad(rsa,sha256)
> > (pkcs1pad(rsa-generic,sha256))
> > [2.562511] SELinux:  Class alg_socket not defined in policy.
> > [4.168887] alg: skcipher-ddst: Test 5 failed (invalid result) on
> > encryption for qat_aes_cbc
> > [4.217866] alg: skcipher-ddst: Chunk test 1 failed on encryption
> > at page 0 for qat_aes_ctr
> > [4.282042] alg: skcipher: Test 4 failed (invalid result) on
> > encryption for qat_aes_xts
> > [4.367682] alg: akcipher: encrypt test failed. Invalid output
> > [4.395210] alg: akcipher: test 1 failed for qat-rsa, err=-22
> > [4.431827] alg: dh: generate public key test failed. Invalid output
> > [4.431829] alg: dh: test failed on vector 1, err=-22
> > 
> > 
> > 83:00.0 Co-processor: Intel Corporation DH895XCC Series QAT
> > Subsystem: Intel Corporation Device 
> > Physical Slot: 2
> > Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> > Stepping- SERR+ FastB2B- DisINTx+
> > Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
> > SERR-  > Latency: 0, Cache Line Size: 32 bytes
> > Interrupt: pin A routed to IRQ 35
> > NUMA node: 1
> > Region 0: Memory at fb90 (64-bit, prefetchable) [size=512K]
> > Region 2: Memory at fbd4 (64-bit, non-prefetchable) [size=256K]
> > Region 4: Memory at fbd0 (64-bit, non-prefetchable) [size=256K]
> > Capabilities: [b0] MSI: Enable- Count=1/1 Maskable+ 64bit+
> > Address:   Data: 
> > Masking:   Pending: 
> > Capabilities: [60] MSI-X: Enable+ Count=33 Masked-
> > Vector table: BAR=2 offset=0003b000
> > PBA: BAR=2 offset=0003b800
> > Capabilities: [6c] Power Management version 3
> > Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-
> > ,D3cold-)
> > Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
> > Capabilities: [74] Express (v2) Endpoint, MSI 00
> > DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s <128ns, L1 <1us
> > ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset+ SlotPowerLimit 0.000W
> > DevCtl: Report errors: Correctable+ Non-Fatal+ Fatal+ Unsupported+
> > RlxdOrd- ExtTag+ PhantFunc- AuxPwr- NoSnoop+ FLReset-
> > MaxPayload 256 bytes, MaxReadReq 1024 bytes
> > DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr- TransPend-
> > LnkCap: Port #0, Speed 5GT/s, Width x16, ASPM L0s, Exit Latency L0s
> > <512ns, L1 unlimited
> > ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp-
> > LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk-
> > ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
> > LnkSta: Speed 5GT/s, Width x16, TrErr- Train- SlotClk- DLActive-
> > BWMgmt- ABWMgmt-
> > DevCap2: Completion Timeout: Range B, TimeoutDis+, LTR-, OBFF Not
> > Supported
> > AtomicOpsCap: 32bit- 64bit- 128bitCAS-
> > DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF
> > Disabled
> > AtomicOpsCtl: ReqEn-
> > LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis-
> >  Transmit Margin: Normal Operating Range, EnterModifiedCompliance-
> > ComplianceSOS-
> >  Compliance De-emphasis: -6dB
> > LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-,
> > EqualizationPhase1-
> >  EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-
> > Capabilities: [100 v1] Advanced Error Reporting
> > 

RE: Alg errors with Intel QAT Card

[Benedetto, Salvatore]

Hi Raj,

I've compiled and tested kernel 4.12.0-rc4 and I can't reproduce your issue.
Are you seeing any of this with a previous kernel version? If not, git bisect 
might
help us finding the root-cause.
Have you tried with another platform/hw?

Regards,
Salvatore

> -Original Message-
> From: linux-crypto-ow...@vger.kernel.org [mailto:linux-crypto-
> ow...@vger.kernel.org] On Behalf Of Raj Ammanur
> Sent: Friday, June 9, 2017 7:37 PM
> To: Linux Crypto Mailing List 
> Subject: Alg errors with Intel QAT Card
> 
> Hi
> 
> I am seeing the below errors after  installing an Intel QAT card
> and loading the upstreamed qat_dh895xcc and intel_qat modules.
> 
> Have others seen similar errors and know if this is a known issue
> and a fix exists or know whats going on ? This is with 4.12.0-rc4+
> version of the kernel.
> 
> Any help is sincerely appreciated.
> 
> thanks
> --Raj
> 
> 
> [3.639046] dh895xcc :00:0b.0: qat_dev0 started 12 acceleration engines
> [4.168887] alg: skcipher-ddst: Test 5 failed (invalid result) on
> encryption for qat_aes_cbc
> [4.217866] alg: skcipher-ddst: Chunk test 1 failed on encryption
> at page 0 for qat_aes_ctr
> [4.282042] alg: skcipher: Test 4 failed (invalid result) on
> encryption for qat_aes_xts
> [4.395210] alg: akcipher: test 1 failed for qat-rsa, err=-22
> [root@dhcp-swlab-681 ~]# dmesg | grep -i alg
> [1.499336] alg: No test for pkcs1pad(rsa,sha256)
> (pkcs1pad(rsa-generic,sha256))
> [2.562511] SELinux:  Class alg_socket not defined in policy.
> [4.168887] alg: skcipher-ddst: Test 5 failed (invalid result) on
> encryption for qat_aes_cbc
> [4.217866] alg: skcipher-ddst: Chunk test 1 failed on encryption
> at page 0 for qat_aes_ctr
> [4.282042] alg: skcipher: Test 4 failed (invalid result) on
> encryption for qat_aes_xts
> [4.367682] alg: akcipher: encrypt test failed. Invalid output
> [4.395210] alg: akcipher: test 1 failed for qat-rsa, err=-22
> [4.431827] alg: dh: generate public key test failed. Invalid output
> [4.431829] alg: dh: test failed on vector 1, err=-22
> 
> 
> 83:00.0 Co-processor: Intel Corporation DH895XCC Series QAT
> Subsystem: Intel Corporation Device 
> Physical Slot: 2
> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR+ FastB2B- DisINTx+
> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
> SERR-  Latency: 0, Cache Line Size: 32 bytes
> Interrupt: pin A routed to IRQ 35
> NUMA node: 1
> Region 0: Memory at fb90 (64-bit, prefetchable) [size=512K]
> Region 2: Memory at fbd4 (64-bit, non-prefetchable) [size=256K]
> Region 4: Memory at fbd0 (64-bit, non-prefetchable) [size=256K]
> Capabilities: [b0] MSI: Enable- Count=1/1 Maskable+ 64bit+
> Address:   Data: 
> Masking:   Pending: 
> Capabilities: [60] MSI-X: Enable+ Count=33 Masked-
> Vector table: BAR=2 offset=0003b000
> PBA: BAR=2 offset=0003b800
> Capabilities: [6c] Power Management version 3
> Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-
> ,D3cold-)
> Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
> Capabilities: [74] Express (v2) Endpoint, MSI 00
> DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s <128ns, L1 <1us
> ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset+ SlotPowerLimit 0.000W
> DevCtl: Report errors: Correctable+ Non-Fatal+ Fatal+ Unsupported+
> RlxdOrd- ExtTag+ PhantFunc- AuxPwr- NoSnoop+ FLReset-
> MaxPayload 256 bytes, MaxReadReq 1024 bytes
> DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr- TransPend-
> LnkCap: Port #0, Speed 5GT/s, Width x16, ASPM L0s, Exit Latency L0s
> <512ns, L1 unlimited
> ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp-
> LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk-
> ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
> LnkSta: Speed 5GT/s, Width x16, TrErr- Train- SlotClk- DLActive-
> BWMgmt- ABWMgmt-
> DevCap2: Completion Timeout: Range B, TimeoutDis+, LTR-, OBFF Not
> Supported
> AtomicOpsCap: 32bit- 64bit- 128bitCAS-
> DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF
> Disabled
> AtomicOpsCtl: ReqEn-
> LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis-
>  Transmit Margin: Normal Operating Range, EnterModifiedCompliance-
> ComplianceSOS-
>  Compliance De-emphasis: -6dB
> LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-,
> EqualizationPhase1-
>  EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-
> Capabilities: [100 v1] Advanced Error Reporting
> UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF-
> MalfTLP- ECRC- UnsupReq- ACSViol-
> UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF-
> MalfTLP- ECRC- UnsupReq- ACSViol-
> UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+
> MalfTLP+ ECRC- UnsupReq- ACSViol-
> CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
> CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout-