From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 217805] Qualcomm NFA725A on T14s AMD Gen3: Bluetooth: hci0: Failed to send headers (or body or access otp area)
Date: Thu, 31 Aug 2023 13:26:08 +0000 [thread overview]
Message-ID: <bug-217805-62941-zvZngtQmsF@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-217805-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=217805
--- Comment #2 from François Armand (fanf42@gmail.com) ---
For info, I find that subject: https://superuser.com/a/1451102
So I tried to disable bluetooth in bios, boot, re-enable bluetooth in bios.
With that, I was able to "unblock" the bluetooth adaptater in rfkill.
But I still didn't have any controler listed in `bluethoothctl list`.
I then tried to disable laptot battery ("power > servicing" option in bios) to
see if a full cold restart does something.
It does: I've came back to the initial state, where the controler can't be
enabled at all.
I tried the disable-then-enable-bluetooth-in-bios trick, but that time it
doesn't do anything.
I also notice than early in boot, I have that message:
---
kernel: usb usb1-port3: connect-debounce failed
---
Which seems to be link to the bluetooth controler (I don't have the message
when bluetooth is disabled in bios).
So it looks like an hardware problem right?
--
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:[~2023-08-31 13:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 8:21 [Bug 217805] New: Qualcomm NFA725A on T14s AMD Gen3: Bluetooth: hci0: Failed to send headers (or body or access otp area) bugzilla-daemon
2023-08-28 7:17 ` [Bug 217805] " bugzilla-daemon
2023-08-31 13:26 ` bugzilla-daemon [this message]
2023-12-08 8:23 ` 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-217805-62941-zvZngtQmsF@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