This bug was fixed in the package linux - 5.15.0-22.22
---------------
linux (5.15.0-22.22) jammy; urgency=medium
* jammy/linux: 5.15.0-22.22 -proposed tracker (LP: #1960290)
-- Paolo Pisati <paolo.pis...@canonical.com> Tue, 08 Feb 2022 10:48:49
+0100
** Changed in: linux (Ubuntu Jammy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1933301
Title:
[uacc-0623] hisi_sec2 fail to alloc uacce
Status in kunpeng920:
Fix Committed
Status in kunpeng920 ubuntu-20.04-hwe series:
Fix Committed
Status in kunpeng920 ubuntu-21.10 series:
Fix Released
Status in kunpeng920 ubuntu-22.04 series:
Fix Committed
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Impish:
Fix Released
Status in linux source package in Jammy:
Fix Released
Bug description:
SRU Justification
=================
[Impact]
* Users with HiSilicon Security Engine (SEC) version 2 controller fail to
allocate Uacce.
[Fix]
* upstream 183b60e005975d3c84c22199ca64a9221e620fb6 crypto: hisilicon/qm -
modify the uacce mode check
[Test Plan]
* Deploy Ubuntu Focal with HWE 5.13 kernel to a Kunpeng920 chip with
HiSilicon Security Engine (SEC) version 2 controller
* Boot the system
* 'dmesg | grep "fail to alloc uacce"' and you will see complains from
hisi_sec2. For example: [ 27.015484] hisi_sec2 0000:b6:00.0: fail to alloc
uacce (-22)
[Where problems could occur]
* The regression can be considered as low, since it is HiSilicon crypto
system specific
====== Original Bug Description ======
[Bug Description]
ubuntu 20.04.2 boot system and fail to alloc uacce (-22)
[Steps to Reproduce]
1) boot ubuntu 20.04.2 system
2) dmesg | grep fail
[Actual Results]
[ 27.000086] cma: cma_alloc: alloc failed, req-size: 4 pages, ret: -12
[ 27.006515] hisi_sec2 0000:b6:00.0: Failed to enable PASID
[ 27.012043] hisi_sec2 0000:b6:00.0: Adding to iommu group 45
[ 27.015484] hisi_sec2 0000:b6:00.0: fail to alloc uacce (-22)
[Expected Results]
no fail
[Reproducibility]
100%
[Additional information]
(Firmware version, kernel version, affected hardware, etc. if required):
[Resolution]
this following patches will solve this bug.
commit f8408d2b79b834f79b6c578817e84f74a85d2190
Author: Kai Ye <yeka...@huawei.com>
Date: Tue Jan 5 14:16:42 2021 +0800
crypto: hisilicon - add ZIP device using mode parameter
Add 'uacce_mode' parameter for ZIP, which can be set as 0(default) or 1.
'0' means ZIP is only registered to kernel crypto, and '1' means it's
registered to both kernel crypto and UACCE.
Signed-off-by: Kai Ye <yeka...@huawei.com>
Reviewed-by: Zhou Wang <wangzh...@hisilicon.com>
Reviewed-by: Zaibo Xu <xuza...@huawei.com>
Signed-off-by: Herbert Xu <herb...@gondor.apana.org.au>
commit bedd04e4aa1434d2f0f038e15bb6c48ac36876e1
Author: Kai Ye <yeka...@huawei.com>
Date: Tue Jan 5 14:16:43 2021 +0800
crypto: hisilicon/hpre - register HPRE device to uacce
commit 34932a6033be3c0088935c334e4dc5ad43dcb0cc
Author: Kai Ye <yeka...@huawei.com>
Date: Tue Jan 5 14:16:44 2021 +0800
crypto: hisilicon/sec - register SEC device to uacce
To manage notifications about this bug go to:
https://bugs.launchpad.net/kunpeng920/+bug/1933301/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
