[Bug 218863] amd-pmf AMDI0102:00: ta invoke cmd init failed err: 60005

[Bug 218863] amd-pmf AMDI0102:00: ta invoke cmd init failed err: 60005

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=218863

--- Comment #24 from Shyam Sundar S K (AMD) (shyam-sundar.s-k@amd.com) ---
I see that extra debug logs, unfortunately that does not provide any hints on
why you are seeing the TEE error.

Can you please dump the policy binary and send the debug output? basically, I
am looking at:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/platform/x86/amd/pmf/tee-if.c?h=v6.10#n463

for this to happen, you will need to enable CONFIG_AMD_PMF_DEBUG.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching someone on the CC list of the bug.

[Bug 218863] amd-pmf AMDI0102:00: ta invoke cmd init failed err: 60005

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=218863

--- Comment #25 from Artem S. Tashkinov (aros@gmx.com) ---
(In reply to Shyam Sundar S K (AMD) from comment #24)
> I see that extra debug logs, unfortunately that does not provide any hints
> on why you are seeing the TEE error.
> 
> Can you please dump the policy binary and send the debug output? basically,
> I am looking at:
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/
> drivers/platform/x86/amd/pmf/tee-if.c?h=v6.10#n463
> 
> for this to happen, you will need to enable CONFIG_AMD_PMF_DEBUG.

Could it be done from Windows?

I cannot rebuild the kernel currently.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching someone on the CC list of the bug.

[Bug 218863] amd-pmf AMDI0102:00: ta invoke cmd init failed err: 60005

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=218863

--- Comment #26 from Shyam Sundar S K (AMD) (shyam-sundar.s-k@amd.com) ---
I don't think Windows PMF driver offers a way to dump the policy binary. You
will have to build a kernel to get to this point.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching someone on the CC list of the bug.

[Bug 218863] amd-pmf AMDI0102:00: ta invoke cmd init failed err: 60005

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=218863

blunted.tip@proton.me changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |blunted.tip@proton.me

--- Comment #27 from blunted.tip@proton.me ---
I have encountered the same bug:
- HP Elitebook 845 G10 7840U
- Linux version 6.10.2-061002-generic (ubuntu upstream kernel build)


Here are relevant amd-pmf logs:
kernel: amd-pmf AMDI0102:00: Policy Binary size: 6672 bytes
kernel: amd-pmf AMDI0102:00: ta invoke cmd init failed err: 60005
kernel: amd-pmf AMDI0102:00: registered PMF device successfully
kernel: amd-pmf AMDI0102:00: Sending heartbeat to SBIOS

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching someone on the CC list of the bug.

[Bug 218863] amd-pmf AMDI0102:00: ta invoke cmd init failed err: 60005

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=218863

--- Comment #28 from blunted.tip@proton.me ---
Created attachment 306679
  --> https://bugzilla.kernel.org/attachment.cgi?id=306679&action=edit
elitebook 845 7840U policy binary dump, 6672 bytes

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching someone on the CC list of the bug.

[Bug 218863] amd-pmf AMDI0102:00: ta invoke cmd init failed err: 60005

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=218863

--- Comment #29 from blunted.tip@proton.me ---
Comment on attachment 306679
  --> https://bugzilla.kernel.org/attachment.cgi?id=306679
elitebook 845 7840U policy binary dump, 6672 bytes

The output was created with:

grep 'kernel: (pb):' /var/log/kern.log| pcre2grep -o1 '(kernel: .+)' | grep -v
'ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff' > /tmp/pb-1.txt

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching someone on the CC list of the bug.

[Bug 218863] amd-pmf AMDI0102:00: ta invoke cmd init failed err: 60005

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=218863

--- Comment #30 from Artem S. Tashkinov (aros@gmx.com) ---
Shyam Sundar S K,

Have you had a chance to check out the dump?

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching someone on the CC list of the bug.

[Bug 218863] amd-pmf AMDI0102:00: ta invoke cmd init failed err: 60005

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=218863

--- Comment #31 from Shyam Sundar S K (AMD) (shyam-sundar.s-k@amd.com) ---
I apologize for the delay. Upon reviewing the dump, my preliminary analysis
indicates that the critical security metadata required for the ASP to decrypt
is missing. I am currently checking an in-house HP laptop to determine if this
issue is present on other devices as well.

If the problem is widespread, I will collaborate with the BIOS team to deploy a
solution. If it is not, you will need to contact HP to obtain an updated BIOS.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching someone on the CC list of the bug.

[Bug 218863] amd-pmf AMDI0102:00: ta invoke cmd init failed err: 60005

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=218863

--- Comment #32 from Artem S. Tashkinov (aros@gmx.com) ---
(In reply to Shyam Sundar S K (AMD) from comment #31)
> I apologize for the delay. Upon reviewing the dump, my preliminary analysis
> indicates that the critical security metadata required for the ASP to
> decrypt is missing. I am currently checking an in-house HP laptop to
> determine if this issue is present on other devices as well.
> 
> If the problem is widespread, I will collaborate with the BIOS team to
> deploy a solution. If it is not, you will need to contact HP to obtain an
> updated BIOS.

Thanks a lot!

Does AMD have the power to force OEMs to fix the behaviour of their BIOSes
under Linux? There's another very serious bug in HP laptops that the company is
unwilling to fix:

https://bugzilla.kernel.org/show_bug.cgi?id=218305

I reported it to them over a year ago.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching someone on the CC list of the bug.

[Bug 218863] amd-pmf AMDI0102:00: ta invoke cmd init failed err: 60005

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=218863

--- Comment #33 from Shyam Sundar S K (AMD) (shyam-sundar.s-k@amd.com) ---
You are correct. It is quite challenging to push OEMs for a BIOS update.
However, if the issue affects multiple products and can be reproduced on
Windows, we can build a case around it.

Please note that this process will take a considerable amount of time.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching someone on the CC list of the bug.

[Bug 218863] amd-pmf AMDI0102:00: ta invoke cmd init failed err: 60005

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=218863

--- Comment #34 from Shyam Sundar S K (AMD) (shyam-sundar.s-k@amd.com) ---
I did attempt on multiple HP systems and could not reproduce this issue
in-house. After having a closer look at a policy binary, it is missing the
metadata required for ASP to process it and hence you see this error.

I am planning to push a newer TA Firmware next week. You can give it a try to
see if that addresses your problem. Else, you may have to file a ticket with HP
to get this sorted out.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching someone on the CC list of the bug.

[Bug 218863] amd-pmf AMDI0102:00: ta invoke cmd init failed err: 60005

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=218863

Tomáš Mark (tomas@digitalspace.name) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tomas@digitalspace.name

--- Comment #35 from Tomáš Mark (tomas@digitalspace.name) ---
The same on 

OS: Kubuntu 24.04.1 LTS x86_64 
Host: HP ZBook Firefly 14 inch G10 A Mobile Workstation PC SBKPF 
Kernel: 6.8.0-45-lowlatency 
Uptime: 22 mins 
Packages: 4630 (dpkg), 7 (flatpak), 21 (snap) 
Shell: bash 5.2.21 
Resolution: 2560x1600, 3840x2160 
DE: Plasma 5.27.11 
WM: KWin 
WM Theme: Breeze 
Theme: [Plasma], Breeze [GTK2/3] 
Icons: breeze-dark [Plasma], breeze-dark [GTK2/3] 
Terminal: konsole 
CPU: AMD Ryzen 7 PRO 7840HS w/ Radeon 780M Graphics (16) @ 4.290GHz 
GPU: AMD ATI c3:00.0 Phoenix1 
Memory: 4193MiB / 58760MiB 

log
Oct 05 09:16:00 nb-vortex kernel: amd-pmf AMDI0102:00: ta invoke cmd init
failed err: 60005
Oct 05 09:16:00 nb-vortex kernel: amd-pmf AMDI0102:00: registered PMF device
successfully

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching someone on the CC list of the bug.

[Bug 218863] [BAD FIRMWARE] amd-pmf AMDI0102:00: ta invoke cmd init failed err: 60005

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=218863

Artem S. Tashkinov (aros@gmx.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|amd-pmf AMDI0102:00: ta     |[BAD FIRMWARE] amd-pmf
                   |invoke cmd init failed err: |AMDI0102:00: ta invoke cmd
                   |60005                       |init failed err: 60005

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching someone on the CC list of the bug.

[Bug 218863] [BAD FIRMWARE] amd-pmf AMDI0102:00: ta invoke cmd init failed err: 60005

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=218863

Yaroslav (yaroslav@lll.gd) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |yaroslav@lll.gd

--- Comment #36 from Yaroslav (yaroslav@lll.gd) ---
Have the same message

System:

  Host: elitebook Kernel: 6.13.3-cachyos1.fc41.x86_64 arch: x86_64 bits: 64
    compiler: gcc v: 14.2.1 clocksource: tsc
  Desktop: KDE Plasma v: 6.3.0 tk: Qt v: N/A wm: kwin_wayland with: krunner
    vt: 2 dm: SDDM Distro: Fedora Linux 41 (KDE Plasma)
Machine:
  Type: Laptop System: HP product: HP EliteBook 845 14 inch G10 Notebook PC
  Mobo: HP model: 8B6E v: KBC Version 60.34.00
    part-nu: 818N0EA#ABU UEFI: HP v: 82 Ver. 01.07.00
    date: 11/14/2024
CPU:
  model: AMD Ryzen 9 PRO 7940HS w/ Radeon 780M

[    5.375196] amd-pmf AMDI0102:00: ta invoke cmd init failed err: 60005
[    5.396214] amd-pmf AMDI0102:00: registered PMF device successfully

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching someone on the CC list of the bug.

[Bug 218863] [BAD FIRMWARE] amd-pmf AMDI0102:00: ta invoke cmd init failed err: 60005

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=218863

--- Comment #37 from Tomáš Mark (tomas@digitalspace.name) ---
Good morning,
I would like to ask if there is any news in this area?

Thank you.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching someone on the CC list of the bug.

[Bug 218863] [BAD FIRMWARE] amd-pmf AMDI0102:00: ta invoke cmd init failed err: 60005

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=218863

Artem S. Tashkinov (aros@gmx.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |WILL_NOT_FIX

--- Comment #38 from Artem S. Tashkinov (aros@gmx.com) ---
(In reply to Tomáš Mark from comment #37)
> Good morning,
> I would like to ask if there is any news in this area?
> 
> Thank you.

AFAIK it's a firmware issue, so no news.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching someone on the CC list of the bug.

[Bug 218863] [BAD FIRMWARE] amd-pmf AMDI0102:00: ta invoke cmd init failed err: 60005

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=218863

--- Comment #39 from blunted.tip@proton.me ---
On my HP Elitebook 845 G10 laptop, I haven't seen the error in a long time,
possibly fixed by the BIOS updates since late last year.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching someone on the CC list of the bug.

[Bug 218863] [BAD FIRMWARE] amd-pmf AMDI0102:00: ta invoke cmd init failed err: 60005

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=218863

--- Comment #40 from Laurent Bonnaud (L.Bonnaud@laposte.net) ---
Intriguing.  I am using a similar laptop and I still see this error with kernel
6.14.8:

# journalctl | grep amd-pmf
May 24 10:42:02 vougeot kernel: amd-pmf AMDI0102:00: Failed to open TA session
(-12)
May 24 10:42:02 vougeot kernel: amd-pmf AMDI0102:00: registered PMF device
successfully

From dmidecode:

        Version: V82 Ver. 01.08.00
        Release Date: 01/14/2025

        Product Name: HP EliteBook 865 16 inch G10 Notebook PC

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching someone on the CC list of the bug.

[Bug 218863] [BAD FIRMWARE] amd-pmf AMDI0102:00: ta invoke cmd init failed err: 60005

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=218863

--- Comment #41 from Artem S. Tashkinov (aros@gmx.com) ---
I can confirm that HP has actually fixed the issue in the latest BIOS/EFI.

Type: BIOS-System Firmware
Version: 01.09.00 Rev.A
Release date: May 9, 2025

- General bug fixes.
- Fixes a BitLocker issue that occurs after a BIOS update is run.
- Addresses security vulnerabilities CVE-2024-36347.
- Improves battery health protection and reporting accuracy.
- Provides general stability improvements.
- Includes the following firmware: AMD Graphics Output Protocol (GOP) Firmware,
version 3.8.9 AMD PSP Firmware, version 0.2D.0.83 AMD SMU Firmware, version
0.76.93.0 Embedded Controller (EC) Firmware, version 60.37.00 Intel/Realtek
UEFI PXE ROM, version 2.046 TI Power Delivery (PD) Firmware, version 4.2.0

Some issues remain but they are totally harmless:

hp_wmi: query 0x4 returned error 0x5 (
https://bugzilla.kernel.org/show_bug.cgi?id=201881 )
nvme nvme0: using unchecked data buffer (not an issue per se, see
https://bbs.archlinux.org/viewtopic.php?id=303412 )
block nvme0n1: No UUID available providing old NGUID (This message is currently
logged as a warning but it's not actionable and according to Keith Busch "It's
a harmless informative message".)


(In reply to Laurent Bonnaud from comment #40)
> Intriguing.  I am using a similar laptop and I still see this error with
> kernel 6.14.8:

Update your BIOS.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching someone on the CC list of the bug.