From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 218651] kernel 6.8.2 - Bluetooth bug/dump at boot
Date: Sat, 30 Mar 2024 19:34:01 +0000 [thread overview]
Message-ID: <bug-218651-62941-A5qRoE50sH@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218651-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=218651
kbugreports@proton.me changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kbugreports@proton.me
--- Comment #15 from kbugreports@proton.me ---
I can confirm this bug for / in kernel v6.6.23.
Not that I care about bluetooth, but apparently it also affects usb.
This issue is present at most but not all boots, sometimes it does not occur.
Real world consequence on my system (thinkpad, kabylake) is that external usb
keyboard and mouse are not recognized -> system unusable. Inbuild touchpad
works, so I can initiate a reboot, but the system doesn't power down properly
and still needs a hard reset to complete the "reboot".
If the system happens to boot fine (i.e. the new, unusual output on the boot
screen is missing), those problems don't appear.
Going back to kernel v6.6.22 solve this issue for me.
Hoping / assuming the fix will also be included in the 6.6.24 kernel.
--
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:[~2024-03-30 19:34 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-28 2:10 [Bug 218651] New: kernel 6.8.2 - Bluetooth bug/dump at boot bugzilla-daemon
2024-03-28 2:12 ` [Bug 218651] " bugzilla-daemon
2024-03-28 2:13 ` bugzilla-daemon
2024-03-28 11:00 ` bugzilla-daemon
2024-03-28 11:03 ` bugzilla-daemon
2024-03-28 11:08 ` bugzilla-daemon
2024-03-28 12:48 ` bugzilla-daemon
2024-03-28 12:49 ` bugzilla-daemon
2024-03-28 12:50 ` bugzilla-daemon
2024-03-28 12:52 ` bugzilla-daemon
2024-03-30 1:49 ` bugzilla-daemon
2024-03-30 1:50 ` bugzilla-daemon
2024-03-30 13:59 ` bugzilla-daemon
2024-03-30 15:50 ` bugzilla-daemon
2024-03-30 17:27 ` bugzilla-daemon
2024-03-30 19:34 ` bugzilla-daemon [this message]
2024-03-30 21:52 ` bugzilla-daemon
2024-03-31 15:48 ` bugzilla-daemon
2024-03-31 16:21 ` bugzilla-daemon
2024-03-31 16:56 ` bugzilla-daemon
2024-04-01 20:33 ` bugzilla-daemon
2024-04-02 6:47 ` bugzilla-daemon
2024-04-04 4:45 ` bugzilla-daemon
2024-04-04 5:38 ` bugzilla-daemon
2024-04-04 8:56 ` bugzilla-daemon
2024-04-05 16:35 ` bugzilla-daemon
2024-04-06 6:54 ` 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-218651-62941-A5qRoE50sH@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.