From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 221250] New: intel_ish_ipc: "ISH loader: cmd 2 failed 10" on Lunar Lake Integrated Sensor Hub (ThinkPad X9-14 Gen 1)
Date: Mon, 16 Mar 2026 23:26:05 +0000 [thread overview]
Message-ID: <bug-221250-215701@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=221250
Bug ID: 221250
Summary: intel_ish_ipc: "ISH loader: cmd 2 failed 10" on Lunar
Lake Integrated Sensor Hub (ThinkPad X9-14 Gen 1)
Product: Drivers
Version: 2.5
Hardware: Intel
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: Platform_x86
Assignee: drivers_platform_x86@kernel-bugs.osdl.org
Reporter: thisisamirv@gmail.com
Regression: No
Created attachment 309693
--> https://bugzilla.kernel.org/attachment.cgi?id=309693&action=edit
log
I am observing repeated Intel ISH driver errors on a Lenovo ThinkPad X9-14 Gen
1
with an Intel Lunar Lake CPU running Arch Linux.
# System information
Kernel: 6.19.6-arch1-1
Distribution: Arch Linux
Laptop model: Lenovo ThinkPad X9-14 Gen 1 (21QBS0KV00)
CPU: Intel Core Ultra 7 268V (Lunar Lake)
Architecture: x86_64
# Hardware
lspci:
00:12.0 Serial controller [0700]: Intel Corporation Lunar Lake-M Integrated
Sensor Hub [8086:a845] (rev 10)
# Kernel messages
The following messages appear repeatedly during boot:
intel_ish_ipc 0000:00:12.0: ISH loader: cmd 2 failed 10
intel_ish_ipc 0000:00:12.0: ISH loader: cmd 2 failed 10
intel_ish_ipc 0000:00:12.0: ISH loader: cmd 2 failed 10
# Kernel modules
lsmod | grep ish:
intel_ish_ipc 32768 0
intel_ishtp 86016 1 intel_ish_ipc
# Observations
The system uses the Lunar Lake integrated sensor hub (ISH). The driver
appears to attempt to load firmware but reports repeated "cmd 2 failed 10"
errors.
It is unclear whether:
- the required firmware is missing,
- the device requires new kernel support, or
- this message is expected for unsupported ISH features.
# Attachments
I have attached the following logs:
- full dmesg
- lscpu
- lsmod
- acpidump
Please let me know if additional information would help diagnose the issue.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
reply other threads:[~2026-03-16 23:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-221250-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.