From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 220421] New: intel_pmc_core INT33A1:00: pmc_core: couldn't get DMU telem endpoint -6
Date: Wed, 06 Aug 2025 08:50:34 +0000 [thread overview]
Message-ID: <bug-220421-215701@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=220421
Bug ID: 220421
Summary: intel_pmc_core INT33A1:00: pmc_core: couldn't get DMU
telem endpoint -6
Product: Drivers
Version: 2.5
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: Platform_x86
Assignee: drivers_platform_x86@kernel-bugs.osdl.org
Reporter: mapengyu@gmail.com
Regression: No
Created attachment 308460
--> https://bugzilla.kernel.org/attachment.cgi?id=308460&action=edit
p16g4-6.16-intel-arl-pmc-error-dmesg.txt
- CPU: Intel(R) Core(TM) Ultra 5 225H
- Kernel version (v6.16)
- Exact hardware model (ThinkPad P16s Gen 4)
- Steps to reproduce (Boot up and check dmesg)
- Relevant dmesg output is attached.
Error log:
[ 6.619085] intel_pmc_core INT33A1:00: Assuming a default substate order for
this platform
[ 6.619106] intel_pmc_core INT33A1:00: pmc_core: couldn't get DMU telem
endpoint -6
[ 6.619274] intel_pmc_core INT33A1:00: initialized
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2025-08-06 8:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-06 8:50 bugzilla-daemon [this message]
2025-08-06 9:03 ` [Bug 220421] intel_pmc_core INT33A1:00: pmc_core: couldn't get DMU telem endpoint -6 bugzilla-daemon
2025-08-06 9:07 ` bugzilla-daemon
2025-08-13 3:30 ` bugzilla-daemon
2025-08-19 20:40 ` bugzilla-daemon
2025-08-20 1:19 ` bugzilla-daemon
2025-10-17 10:21 ` bugzilla-daemon
2025-12-22 7:32 ` 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-220421-215701@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.