From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 213829] Intel AX210 Bluetooth controller doesn't start from warm boot
Date: Sat, 13 Nov 2021 17:55:03 +0000 [thread overview]
Message-ID: <bug-213829-62941-vInPdCG4k3@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-213829-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=213829
--- Comment #27 from Marco (rodomar705@protonmail.com) ---
(In reply to Guillaume Binet from comment #26)
> Alright, talking with Intel directly, this patch seems to fix it for 5.15.2:
>
> https://patchwork.kernel.org/project/bluetooth/patch/20211013080511.23945-1-
> kiran.k@intel.com/
>
> I have a bunch of other regressions like GPU hangs with 5.15 but at least I
> see the controller showing up consistently warm reboot after warm reboot.
>
> Can anyone else confirm it works?
Nope, running 5.15.2 and now bluetooth disappears after a reboot. This hasn't
fixed the problem for me, it just changed behaviour.
I can confirm that the patch is present, I do see the message added for that
patch:
...
[ 2470.756299] Bluetooth: hci0: Timed out waiting for suspend events
[ 2470.756315] Bluetooth: hci0: Suspend timeout bit: 6
[ 2470.756345] Bluetooth: hci0: Suspend notifier action (3) failed: -110
[13556.607173] Bluetooth: hci0: Firmware timestamp 2021.39 buildtype 1 build
31878
[13556.611182] Bluetooth: hci0: No device address configured
[13556.611197] Bluetooth: hci0: Found device firmware: intel/ibt-0041-0041.sfi
[13556.611306] Bluetooth: hci0: Boot Address: 0x100800
[13556.611308] Bluetooth: hci0: Firmware Version: 134-39.21
[13556.611310] Bluetooth: hci0: Firmware already loaded
...
But there is no bluetooth adapter available from both my DE nor from
bluetoothctl info command.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2021-11-13 17:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-213829-62941@https.bugzilla.kernel.org/>
2021-09-10 4:41 ` [Bug 213829] Intel AX210 Bluetooth controller doesn't start from warm boot bugzilla-daemon
2021-10-17 18:05 ` bugzilla-daemon
2021-11-02 13:57 ` bugzilla-daemon
2021-11-02 20:02 ` bugzilla-daemon
2021-11-11 1:11 ` bugzilla-daemon
2021-11-11 3:12 ` bugzilla-daemon
2021-11-13 3:43 ` bugzilla-daemon
2021-11-13 9:19 ` bugzilla-daemon
2021-11-13 17:55 ` bugzilla-daemon [this message]
2021-11-14 8:07 ` bugzilla-daemon
2021-11-14 14:36 ` bugzilla-daemon
2021-11-25 12:19 ` bugzilla-daemon
2021-11-26 14:49 ` bugzilla-daemon
2022-01-02 20:37 ` bugzilla-daemon
2022-01-02 21:07 ` bugzilla-daemon
2022-01-06 12:58 ` bugzilla-daemon
2022-01-06 13:03 ` 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-213829-62941-vInPdCG4k3@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.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 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).