All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 221481] btintel_pcie: suspend fails with -EBUSY on Intel Lunar Lake (s2idle)
Date: Wed, 19 Aug 2026 17:34:28 +0000	[thread overview]
Message-ID: <bug-221481-62941-zuesNp2gjZ@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-221481-62941@https.bugzilla.kernel.org/>

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

markgerlach@mailbox.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |markgerlach@mailbox.org

--- Comment #2 from markgerlach@mailbox.org ---
Laptop: Lenovo ThinkPad E14 Gen 7
CPU: Intel Core Ultra 7 258V
Kernel: 7.1.8-200.fc44.x86_64
Distro: Fedora 44 Gnome Wayland
Bluetooth device: 00:14.7 Bluetooth [0d11]: Intel Corporation Device
[8086:a876] (rev 10)

Additional detail regarding firmware:

In dmesg, the driver fails to load the firmware:
`Bluetooth: hci0: Failed to load Intel firmware file
intel/ibt-0190-01a1-iml.sfi (-2)`

Checking `/lib/firmware/intel/` shows that `ibt-0190-0041` and `ibt-0190-0291`
are present in linux-firmware, but revision `01a1` (`ibt-0190-01a1-iml.sfi`) is
missing.

This missing firmware leaves the Bluetooth controller in an uninitialized
state, which directly leads to the D2 suspend timeout (error -16)

[s2idle] failed.

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

You are receiving this mail because:
You are the assignee for the bug.

      parent reply	other threads:[~2026-08-19 17:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-07 19:28 [Bug 221481] New: btintel_pcie: suspend fails with -EBUSY on Intel Lunar Lake (s2idle) bugzilla-daemon
2026-05-22  9:04 ` [Bug 221481] " bugzilla-daemon
2026-08-19 17:34 ` 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-221481-62941-zuesNp2gjZ@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-bluetooth@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.