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: Sat, 19 Jul 2025 11:07:29 +0000 [thread overview]
Message-ID: <bug-220341-62941-Y9OdNxAEpo@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220341-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=220341
--- Comment #17 from Nicolas BARANGER (nicolas.baranger@3xo.fr) ---
@Martin Hignett
What about mainline (6.16-rc6) ?
https://git.kernel.org/torvalds/t/linux-6.16-rc6.tar.gz
or
git clone --depth=1
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
(I had a lots of IO and netfs issues using Linux 6.10 to 6.13.1 ...)
Regards
Nicolas
--
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-19 11:07 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
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 [this message]
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-Y9OdNxAEpo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox