From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 214345] New: Bluetooth does not work, which worked earlier
Date: Tue, 07 Sep 2021 18:59:20 +0000 [thread overview]
Message-ID: <bug-214345-62941@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=214345
Bug ID: 214345
Summary: Bluetooth does not work, which worked earlier
Product: Drivers
Version: 2.5
Kernel Version: 5.13.9-100.fc33.x86_64, 5.13.10-100.fc33.x86_64,
5.13.12-100.fc33.x86_64
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: Bluetooth
Assignee: linux-bluetooth@vger.kernel.org
Reporter: kiran.telukunta@indiayouth.info
Regression: No
I have following model of bluetooth dongle:
Bus 005 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle
(HCI mode)
and produces following failed mode status:
sudo systemctl status bluetooth
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor
preset: enabled)
Active: active (running) since Tue 2021-09-07 20:34:23 CEST; 16min ago
Docs: man:bluetoothd(8)
Main PID: 1023 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 38343)
Memory: 2.2M
CPU: 27ms
CGroup: /system.slice/bluetooth.service
└─1023 /usr/libexec/bluetooth/bluetoothd
Sep 07 20:34:23 saraswathi bluetoothd[1023]: Failed to set mode: Blocked
through rfkill (0x12) <<<<<<<<<<<<<<-----------------------
Sep 07 20:34:48 saraswathi bluetoothd[1023]: Endpoint registered: sender=:1.214
path=/MediaEndpoint/A2DPSource/VENDOR/LDAC
Sep 07 20:34:48 saraswathi bluetoothd[1023]: Endpoint registered: sender=:1.214
path=/MediaEndpoint/A2DPSource/VENDOR/APTXHD
Sep 07 20:34:48 saraswathi bluetoothd[1023]: Endpoint registered: sender=:1.214
path=/MediaEndpoint/A2DPSource/VENDOR/APTX
Sep 07 20:34:48 saraswathi bluetoothd[1023]: Endpoint registered: sender=:1.214
path=/MediaEndpoint/A2DPSource/AAC
Sep 07 20:34:48 saraswathi bluetoothd[1023]: Endpoint registered: sender=:1.214
path=/MediaEndpoint/A2DPSource/SBC
Sep 07 20:34:48 saraswathi bluetoothd[1023]: Endpoint registered: sender=:1.214
path=/MediaEndpoint/A2DPSink/VENDOR/APTXHD
Sep 07 20:34:48 saraswathi bluetoothd[1023]: Endpoint registered: sender=:1.214
path=/MediaEndpoint/A2DPSink/VENDOR/APTX
Sep 07 20:34:48 saraswathi bluetoothd[1023]: Endpoint registered: sender=:1.214
path=/MediaEndpoint/A2DPSink/AAC
Sep 07 20:34:48 saraswathi bluetoothd[1023]: Endpoint registered: sender=:1.214
path=/MediaEndpoint/A2DPSink/SBC
The dongle is not getting connected in the following kernel versions:
5.13.9-100.fc33.x86_64
5.13.10-100.fc33.x86_64
5.13.12-100.fc33.x86_64
It worked couple of months before so it should be working in the kernel
kernel-5.13.6-0.
Let me know if you need any other information.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2021-09-07 18:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-214345-62941@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.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.