Public bug reported:

ACPI table is updated for PKA (public key accelerator) HW on bluefield
platforms (by Mellanox/Nvidia).

Platform dependant memory addresses are now defined in ACPI table rather than 
defining them in the driver code.
This requires an update in the PKA driver to read these platform dependant 
memory addresses from ACPI.

Without this update PKA driver won't function as required and kernel
traces will be seen on startup/loading.

SRU Justification:

[Impact]
* ACPI definitions are updated for PKA (public key accelerator) HW on Bluefield 
platforms (by Mellnox/Nvidia).
* ACPI update requires PKA driver update, else kernel traces will be seen on 
startup.
* PKA driver won't be loaded and PKA HW will be inaccessible.

[Fix]
* "pka: Use memory addresses defined in ACPI table"

[Testcase]
* On bluefield system startup check if PKA driver is loaded without
 any errors. Ex:#dmesg | grep -i pka

[Regression Potential]
* For systems where the ACPI update is not applied but PKA driver update is 
 applied, will see kernel traces as driver will try to read definitions from 
 ACPI which are not present. This will lead to failure in loading of PKA driver 
 and PKA HW will be inaccessible. Solution to this is to update ACPI. All new
 bluefield images will have updated ACPI definitions.
* Example kernel trace: [    9.970155] Call trace:
                        [    9.972625] pka_drv_probe+0x41c/0x5f0 [mlxbf_pka]

** Affects: linux-bluefield (Ubuntu)
     Importance: Undecided
         Status: New

** Description changed:

  ACPI table is updated for PKA (public key accelerator) HW on bluefield
  platforms (by Mellanox/Nvidia).
  
  Platform dependant memory addresses are now defined in ACPI table rather than 
defining them in the driver code.
  This requires an update in the PKA driver to read these platform dependant 
memory addresses from ACPI.
  
  Without this update PKA driver won't function as required and kernel
  traces will be seen on startup/loading.
  
  SRU Justification:
-  
+ 
  [Impact]
  * ACPI definitions are updated for PKA (public key accelerator) HW on 
Bluefield platforms (by Mellnox/Nvidia).
  * ACPI update requires PKA driver update, else kernel traces will be seen on 
startup.
  * PKA driver won't be loaded and PKA HW will be inaccessible.
-  
+ 
  [Fix]
  * "pka: Use memory addresses defined in ACPI table"
-  
+ 
  [Testcase]
- * On bluefield system startup check if PKA driver is loaded without 
-  any errors. Ex:#dmesg | grep -i pka
+ * On bluefield system startup check if PKA driver is loaded without
+  any errors. Ex:#dmesg | grep -i pka
  
  [Regression Potential]
- * For systems where the ACPI update is not applied but PKA driver update is 
applied, will see kernel traces 
-  as driver will try to read definitions from ACPI which are not present. This 
will lead to failure in 
-  loading of PKA driver and PKA HW will be inaccessible. Solution to this is 
to update ACPI. All new 
-  bluefield images will have updated ACPI definitions.
+ * For systems where the ACPI update is not applied but PKA driver update is 
+  applied, will see kernel traces as driver will try to read definitions from 
+  ACPI which are not present. This will lead to failure in loading of PKA 
driver 
+  and PKA HW will be inaccessible. Solution to this is to update ACPI. All new
+  bluefield images will have updated ACPI definitions.
  * Example kernel trace: [    9.970155] Call trace:
-                         [    9.972625] pka_drv_probe+0x41c/0x5f0 [mlxbf_pka]
+                         [    9.972625] pka_drv_probe+0x41c/0x5f0 [mlxbf_pka]

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1916274

Title:
  PKA ACPI update

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1916274/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to