Embedded Intel® Core™ Processors
Communicate Intel® Core™ Hardware, Software, Firmware, Graphics Concerns
Announcements
FPGA community forums and blogs have moved to the Altera Community. Existing Intel Community members can sign in with their current credentials.

QAT heartbeat with autoreset

SSant31
Beginner
1,601 Views

Hello,

 

I enabled QAT autoreset on error and configured the QAT driver with "--enable-icp-hb-fail-sim" option. I noticed the following when I tried to test with "heartbeat_sim_fail".

 

======================================

# cat /sys/kernel/debug/qat_dh895xcc_0000\:03\:00.0/heartbeat_sim_fail

dh895xcc 0000:03:00.0: adf_heartbeat_simulate_failure for random AE 9, thr 9

 

# cat /sys/kernel/debug/qat_dh895xcc_0000\:03\:00.0/heartbeat

-1

 

dh895xcc 0000:03:00.0: ERROR: QAT is not responding.

dh895xcc 0000:03:00.0: Quiescing device.

dh895xcc 0000:03:00.0: Disable arbiter.

------------[ cut here ]------------

WARNING: CPU: 30 PID: 184 at /home/srini/work/5.1.9/ap/build/tmp/work/ion-ion-linux/qat-dh895x/4.7.0.6-r1/quickassist/qat/drivers/crypto/qat/qat_common/adf_aer.c:205 adf_device_reset_worker+0xd8/0x110 [intel_qat]

QAT: device reset failed. Device is in use

Modules linked in: esp4 sha512_generic ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_set ip_set_hash_ip ipt_REJECT nf_reject_ipv4 xt_policy iptable_nat xt_mark iptable_mangle xt_hashlimit xt_tcpudp xt_CT iptable_raw xt_multiport xt_conntrack xt_NFLOG nfnetlink_log nf_log_ipv4 nf_log_common xt_LOG nf_conntrack_sane nf_co

nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat libcrc32c nf_conntrack x86_pkg_temp_thermal

CPU: 30 PID: 184 Comm: kworker/30:1 Tainted: G     O  4.10.17-yocto-standard #8

Hardware name: CloudGenix ion 7000/To be filled by O.E.M., BIOS ZG0 04/08/2019

Workqueue: qat_device_reset_wq adf_device_reset_worker [intel_qat]

Call Trace:

dump_stack+0x63/0x83

__warn+0xcb/0xf0

warn_slowpath_fmt+0x4f/0x60

adf_device_reset_worker+0xd8/0x110 [intel_qat]

process_one_work+0x1d0/0x480

worker_thread+0x48/0x4e0

kthread+0x108/0x140

? process_one_work+0x480/0x480

? kthread_create_on_node+0x40/0x40

ret_from_fork+0x2c/0x40

---[ end trace 0b5af0b0f873de6a ]---

 

===============================

Some information about the driver and firmware below:

 

==================================================

# cat fw

4.7.0

# cat hw

0

# cat mmp

0.0.1

# ls

fw hw mmp

# pwd

/sys/kernel/debug/qat_dh895xcc_0000:03:00.0/version

==============================================

 

$cat versionfile 

PACKAGE_TYPE=QAT1.7

 

PACKAGE_OS=L

 

PACKAGE_VERSION_MAJOR_NUMBER=4

 

PACKAGE_VERSION_MINOR_NUMBER=7

 

PACKAGE_VERSION_PATCH_NUMBER=0

 

PACKAGE_VERSION_BUILD_NUMBER=00006

=======================================

 

===========================

 

Driver package name: qat1.7.l.4.7.0-00006.tar.gz

 

Linux kernel version: 4.10.17

 

H/W Info:

=================================

CPU Type: Intel(R) Xeon(R) CPU E5-2640 v2 @ 2.00GHz

03:00.0 Co-processor: Intel Corporation DH895XCC Series QAT

==================================

 

What am I missing here?

 

0 Kudos
1 Reply
CarlosAM_INTEL
Moderator
1,344 Views

Hello, @SSant31​:

 

Thank you for contacting Intel Embedded Community.

 

Your Intel(R) QuickAssist Technology [QAT] consultations should be addressed as a reference to the channels listed at the following website:

 

https://01.org/community

 

Best regards,

@Mæcenas_INTEL​.

0 Kudos
Reply