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 08:10:28 +0000 [thread overview]
Message-ID: <bug-220341-62941-GXLjxReXsN@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 #6 from Nicolas BARANGER (nicolas.baranger@3xo.fr) ---
Hi all
Unfortunatly I don't have this laptop anymore (dell xps 15 9530), but from my
remember of last summer issue, rmmod -f followed by insmod don't work as rmmod
-f was not able to remove the module from the kernel.
The only way I found to recover the situation was to forcely reboot the system
.
Also, don't know if it's related but I remmember that I had no issues during
the last 2 weeks I used this laptop (corporate laptop) and that was just after
removing pcie gen5x2 nvme m2 drive end replacing it by a mdadm done with 2 pcie
gen4x4 nvme drive.
Also note that the issue always happens when I was using an Aquantia AQC100S
10gb nic plugged on thunderbolt bus and maybe when cpu total load was higher to
30% on pcie bus
My feeling was an hardware issue at I/O or DMA that kernel don't handle
properly
NB: I was using grub and not systemd-boot
--
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 8: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
2025-07-16 7:17 ` bugzilla-daemon
2025-07-16 8:10 ` bugzilla-daemon [this message]
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-GXLjxReXsN@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.