From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 218863] amd-pmf AMDI0102:00: ta invoke cmd init failed err: 60005
Date: Wed, 07 Aug 2024 09:49:38 +0000 [thread overview]
Message-ID: <bug-218863-215701-fRbyeqXE7D@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 #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.
next prev parent reply other threads:[~2024-08-07 9:49 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 [this message]
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
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-fRbyeqXE7D@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).