Jammy will release a few months later and we are aware of the
development activities of Jammy 5.15 kernel. The patch needs to land
Jammy as well to prevent user's dist-upgrade regression.

My investigation of the patch, 183b60e00597 crypto: hisilicon/qm -
modify the uacce mode check, has clean cherry-pick with Jammy 5.15
master-next, and fixes the issue[1].


Next:
Process to merge 183b60e00597 with Jammy 5.15 kernel along with impish 5.13 
(for up-coming focal-hwe)


[1] Before applying the patch (master-next branch, 5.15.13):


ubuntu@segers:~$ sudo ./collect.sh 
Linux segers 5.15.0-16-generic #16~d20220111t131721~7ec137fc2603 SMP Tue Jan 11 
13:18:16 UTC 20 aarch64 aarch64 aarch64 GNU/Linux
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 20.04.3 LTS
Release:        20.04
Codename:       focal

[    3.408872] cma: cma_alloc: reserved: alloc failed, req-size: 4096 pages, 
ret: -12
[   11.594241] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, 
ret: -12
[   11.636486] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, 
ret: -12
[   11.678612] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, 
ret: -12
[   11.720721] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, 
ret: -12
[   11.762846] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, 
ret: -12
[   11.805032] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, 
ret: -12
[   11.847216] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, 
ret: -12
[   11.889401] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, 
ret: -12
[   11.970515] cma: cma_alloc: reserved: alloc failed, req-size: 4 pages, ret: 
-12
[   12.067413] cma: cma_alloc: reserved: alloc failed, req-size: 4 pages, ret: 
-12
[   13.974371] dw_spi_mmio HISI0173:00: DMA init failed
[   19.448332] sas: Enter sas_scsi_recover_host busy: 0 failed: 0
[   19.820834] sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 0 tries: 1
[   19.852904] sas: Enter sas_scsi_recover_host busy: 0 failed: 0
[   20.224761] sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 0 tries: 1
[   22.956763] cma: cma_alloc: reserved: alloc failed, req-size: 4 pages, ret: 
-12
[   22.966698] cma: cma_alloc: reserved: alloc failed, req-size: 16 pages, ret: 
-12
[   22.982319] hisi_sec2 0000:75:00.0: fail to alloc uacce (-22)
[   22.990846] cma: cma_alloc: reserved: alloc failed, req-size: 4 pages, ret: 
-12
[   22.999914] cma: cma_alloc: reserved: alloc failed, req-size: 16 pages, ret: 
-12
[   23.010710] hisi_sec2 0000:b5:00.0: fail to alloc uacce (-22)


==================
[    0.000000] cma: Reserved 32 MiB at 0x000000007e000000
[    0.000000] Memory: 131307604K/134213440K available (17280K kernel code, 
4572K rwdata, 13820K rodata, 9600K init, 1182K bss, 2873068K reserved, 32768K 
cma-reserved)
[    3.408872] cma: cma_alloc: reserved: alloc failed, req-size: 4096 pages, 
ret: -12
[   11.594241] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, 
ret: -12
[   11.636486] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, 
ret: -12
[   11.678612] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, 
ret: -12
[   11.720721] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, 
ret: -12
[   11.762846] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, 
ret: -12
[   11.805032] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, 
ret: -12
[   11.847216] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, 
ret: -12
[   11.889401] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, 
ret: -12
[   11.970515] cma: cma_alloc: reserved: alloc failed, req-size: 4 pages, ret: 
-12
[   12.067413] cma: cma_alloc: reserved: alloc failed, req-size: 4 pages, ret: 
-12
[   22.956757] cma_alloc: 10 callbacks suppressed
[   22.956763] cma: cma_alloc: reserved: alloc failed, req-size: 4 pages, ret: 
-12
[   22.966698] cma: cma_alloc: reserved: alloc failed, req-size: 16 pages, ret: 
-12
[   22.990846] cma: cma_alloc: reserved: alloc failed, req-size: 4 pages, ret: 
-12
[   22.999914] cma: cma_alloc: reserved: alloc failed, req-size: 16 pages, ret: 
-12
==================


==================
[   22.982319] hisi_sec2 0000:75:00.0: fail to alloc uacce (-22)
[   23.010710] hisi_sec2 0000:b5:00.0: fail to alloc uacce (-22)
==================


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



After apply the patch:


ubuntu@segers:~$ sudo ./collect.sh 
Linux segers 5.15.0-16-generic #16~d20220111t123224~c7a448651f57 SMP Tue Jan 11 
12:33:20 UTC 20 aarch64 aarch64 aarch64 GNU/Linux
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 20.04.3 LTS
Release:        20.04
Codename:       focal

[    3.409019] cma: cma_alloc: reserved: alloc failed, req-size: 4096 pages, 
ret: -12
[   11.604567] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, 
ret: -12
[   11.646821] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, 
ret: -12
[   11.688926] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, 
ret: -12
[   11.731015] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, 
ret: -12
[   11.773110] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, 
ret: -12
[   11.815278] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, 
ret: -12
[   11.857438] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, 
ret: -12
[   11.899604] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, 
ret: -12
[   11.980465] cma: cma_alloc: reserved: alloc failed, req-size: 4 pages, ret: 
-12
[   12.079511] cma: cma_alloc: reserved: alloc failed, req-size: 4 pages, ret: 
-12
[   13.956398] dw_spi_mmio HISI0173:00: DMA init failed
[   19.508395] sas: Enter sas_scsi_recover_host busy: 0 failed: 0
[   19.885185] sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 0 tries: 1
[   19.917295] sas: Enter sas_scsi_recover_host busy: 0 failed: 0
[   20.288927] sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 0 tries: 1
[   22.855815] cma: cma_alloc: reserved: alloc failed, req-size: 4 pages, ret: 
-12
[   22.863792] cma: cma_alloc: reserved: alloc failed, req-size: 16 pages, ret: 
-12
[   22.886230] cma: cma_alloc: reserved: alloc failed, req-size: 4 pages, ret: 
-12
[   22.896009] cma: cma_alloc: reserved: alloc failed, req-size: 16 pages, ret: 
-12


==================
[    0.000000] cma: Reserved 32 MiB at 0x000000007e000000
[    0.000000] Memory: 131307604K/134213440K available (17280K kernel code, 
4572K rwdata, 13820K rodata, 9600K init, 1182K bss, 2873068K reserved, 32768K 
cma-reserved)
[    3.409019] cma: cma_alloc: reserved: alloc failed, req-size: 4096 pages, 
ret: -12
[   11.604567] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, 
ret: -12
[   11.646821] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, 
ret: -12
[   11.688926] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, 
ret: -12
[   11.731015] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, 
ret: -12
[   11.773110] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, 
ret: -12
[   11.815278] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, 
ret: -12
[   11.857438] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, 
ret: -12
[   11.899604] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, 
ret: -12
[   11.980465] cma: cma_alloc: reserved: alloc failed, req-size: 4 pages, ret: 
-12
[   12.079511] cma: cma_alloc: reserved: alloc failed, req-size: 4 pages, ret: 
-12
[   22.855807] cma_alloc: 10 callbacks suppressed
[   22.855815] cma: cma_alloc: reserved: alloc failed, req-size: 4 pages, ret: 
-12
[   22.863792] cma: cma_alloc: reserved: alloc failed, req-size: 16 pages, ret: 
-12
[   22.886230] cma: cma_alloc: reserved: alloc failed, req-size: 4 pages, ret: 
-12
[   22.896009] cma: cma_alloc: reserved: alloc failed, req-size: 16 pages, ret: 
-12
==================


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


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

ubuntu@segers:~$

-- 
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:
  In Progress
Status in kunpeng920 ubuntu-20.04-hwe series:
  In Progress
Status in kunpeng920 ubuntu-21.10 series:
  In Progress
Status in kunpeng920 ubuntu-22.04 series:
  In Progress
Status in linux package in Ubuntu:
  New
Status in linux source package in Impish:
  In Progress
Status in linux source package in Jammy:
  New

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

Reply via email to