From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 220341] Bluetooth crashes about 30-40 minutes after I connect my headphones: "Bluetooth: hci0: Hardware error 0x0a"
Date: Wed, 16 Jul 2025 07:10:37 +0000 [thread overview]
Message-ID: <bug-220341-62941-9yJ1qRwS1V@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220341-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=220341
Paul Menzel (pmenzel+bugzilla.kernel.org@molgen.mpg.de) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mpearson-lenovo@squebb.ca,
| |pmenzel+bugzilla.kernel.org
| |@molgen.mpg.de
--- Comment #4 from Paul Menzel (pmenzel+bugzilla.kernel.org@molgen.mpg.de) ---
Please add the output of `dmesg`, so more hardware details and the loaded
firmware versions are visible. Your log starts with the hardware error below:
Jul 15 11:54:59 martin-work kernel: Bluetooth: hci0: Received hw exception
interrupt
Jul 15 11:54:59 martin-work kernel: Bluetooth: hci0: 00000000: ff 32 87 80
03 01 01 01 03 01 05 0d 02 00 06 0e
Jul 15 11:54:59 martin-work kernel: Bluetooth: hci0: 00000010: 01 00 05 14
0e 1e 00 10 fa 53 06 b0 00 00 00 00
Jul 15 11:54:59 martin-work kernel: Bluetooth: hci0: 00000020: 00 00 00 00
00 00 00 00 fa 04 00 00 00 00 40 04
Jul 15 11:54:59 martin-work kernel: Bluetooth: hci0: 00000030: 10 00 00 00
Jul 15 11:54:59 martin-work kernel: Bluetooth: hci0: 00000000: 10 01 0a
Jul 15 11:54:59 martin-work kernel: Bluetooth: hci0: Hardware error 0x0a
--
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:[~2025-07-16 7:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-15 11:52 [Bug 220341] New: Bluetooth crashes about 30-40 minutes after I connect my headphones: "Bluetooth: hci0: Hardware error 0x0a" bugzilla-daemon
2025-07-15 11:53 ` [Bug 220341] " bugzilla-daemon
2025-07-15 12:13 ` bugzilla-daemon
2025-07-16 0:41 ` bugzilla-daemon
2025-07-16 0:45 ` bugzilla-daemon
2025-07-16 7:10 ` bugzilla-daemon [this message]
2025-07-16 7:17 ` bugzilla-daemon
2025-07-16 8:10 ` bugzilla-daemon
2025-07-16 8:16 ` bugzilla-daemon
2025-07-16 15:27 ` bugzilla-daemon
2025-07-16 15:29 ` bugzilla-daemon
2025-07-17 14:32 ` bugzilla-daemon
2025-07-17 14:33 ` bugzilla-daemon
2025-07-17 19:50 ` bugzilla-daemon
2025-07-17 22:47 ` bugzilla-daemon
2025-07-18 7:12 ` bugzilla-daemon
2025-07-18 7:22 ` bugzilla-daemon
2025-07-19 10:56 ` bugzilla-daemon
2025-07-19 11:07 ` bugzilla-daemon
2025-07-19 11:09 ` bugzilla-daemon
2025-07-19 12:10 ` bugzilla-daemon
2025-08-21 14:29 ` 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-220341-62941-9yJ1qRwS1V@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.