All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 218863] [BAD FIRMWARE] amd-pmf AMDI0102:00: ta invoke cmd init failed err: 60005
Date: Thu, 29 May 2025 10:51:32 +0000	[thread overview]
Message-ID: <bug-218863-215701-siPrr9DR4z@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218863-215701@https.bugzilla.kernel.org/>

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.

      parent reply	other threads:[~2025-05-29 10:51 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-218863-215701@https.bugzilla.kernel.org/>
2024-07-22  5:10 ` [Bug 218863] amd-pmf AMDI0102:00: ta invoke cmd init failed err: 60005 bugzilla-daemon
2024-07-22 20:03 ` bugzilla-daemon
2024-07-23 16:33 ` bugzilla-daemon
2024-08-07  9:36 ` bugzilla-daemon
2024-08-07  9:40 ` bugzilla-daemon
2024-08-07  9:49 ` bugzilla-daemon
2024-08-12 16:03 ` bugzilla-daemon
2024-08-14  3:48 ` bugzilla-daemon
2024-08-14  8:57 ` bugzilla-daemon
2024-08-14 16:26 ` bugzilla-daemon
2024-09-26 10:39 ` bugzilla-daemon
2024-10-05  7:39 ` bugzilla-daemon
2024-10-15 11:58 ` [Bug 218863] [BAD FIRMWARE] " bugzilla-daemon
2025-02-19 10:06 ` bugzilla-daemon
2025-04-06 14:04 ` bugzilla-daemon
2025-04-06 15:55 ` bugzilla-daemon
2025-05-29  7:35 ` bugzilla-daemon
2025-05-29  8:04 ` bugzilla-daemon
2025-05-29 10:51 ` bugzilla-daemon [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-218863-215701-siPrr9DR4z@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.