From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 219387] Bluetooth: hci0: Reading supported features failed (-16)
Date: Wed, 16 Oct 2024 05:51:33 +0000 [thread overview]
Message-ID: <bug-219387-62941-lDclbCBrmZ@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219387-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=219387
The Linux kernel's regression tracker (Thorsten Leemhuis) (regressions@leemhuis.info) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |regressions@leemhuis.info
--- Comment #1 from The Linux kernel's regression tracker (Thorsten Leemhuis) (regressions@leemhuis.info) ---
A few questions:
* Are you testing with vanilla kernels? That "Host: centos Kernel:
5.14.0-514.el9.x86_64" is likely just from a sysinfo query, but looks a bit
suspicious.
* Did this happen with earlier kernels as well? Or which was the last one that
used to work fine?
* Did you update the kernel, or the firmware files as well?
--
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-10-16 5:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-14 16:40 [Bug 219387] New: Bluetooth: hci0: Reading supported features failed (-16) bugzilla-daemon
2024-10-14 16:42 ` [Bug 219387] " bugzilla-daemon
2024-10-16 5:51 ` bugzilla-daemon [this message]
2024-10-16 20:44 ` bugzilla-daemon
2024-10-16 21:02 ` bugzilla-daemon
2024-10-17 0:35 ` bugzilla-daemon
2024-11-03 14:04 ` bugzilla-daemon
2024-11-04 13:02 ` bugzilla-daemon
2024-11-04 13:04 ` bugzilla-daemon
2024-11-04 13:07 ` bugzilla-daemon
2025-01-27 19:02 ` bugzilla-daemon
2025-01-27 19:09 ` bugzilla-daemon
2025-01-28 4:02 ` bugzilla-daemon
2025-07-08 4:46 ` bugzilla-daemon
2025-12-24 15:04 ` bugzilla-daemon
2025-12-24 15:45 ` 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-219387-62941-lDclbCBrmZ@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.