From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 210275] New: Bluetooth stopped working on kernel 5.9
Date: Fri, 20 Nov 2020 07:06:18 +0000 [thread overview]
Message-ID: <bug-210275-62941@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=210275
Bug ID: 210275
Summary: Bluetooth stopped working on kernel 5.9
Product: Drivers
Version: 2.5
Kernel Version: 5.9.8-2
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: Bluetooth
Assignee: linux-bluetooth@vger.kernel.org
Reporter: m11.1l1.f64@gmail.com
Regression: No
Bluetooth stopped working on kernel 5.9
It worked well on kernel 5.8
Output of bluetoothctl:
Agent registered
[bluetooth]# show
No default controller available
[bluetooth]#
On the kernel 5.7:
[bluetooth]# show
Controller 70:66:55:BB:04:B6 (public)
Name: MTN-Lap
Alias: MTN-Lap
Class: 0x00000000
Powered: no
Discoverable: yes
DiscoverableTimeout: 0x00000000
Pairable: yes
UUID: Message Notification Se.. (00001133-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
UUID: OBEX Object Push (00001105-0000-1000-8000-00805f9b34fb)
UUID: Message Access Server (00001132-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
UUID: IrMC Sync (00001104-0000-1000-8000-00805f9b34fb)
UUID: Vendor specific (00005005-0000-1000-8000-0002ee000001)
UUID: Headset AG (00001112-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: Phonebook Access Server (0000112f-0000-1000-8000-00805f9b34fb)
UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb)
UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb)
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: Headset (00001108-0000-1000-8000-00805f9b34fb)
UUID: Audio Source (0000110a-0000-1000-8000-00805f9b34fb)
UUID: OBEX File Transfer (00001106-0000-1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0537
Discovering: no
Roles: central
Roles: peripheral
Advertising Features:
ActiveInstances: 0x00 (0)
SupportedInstances: 0x05 (5)
SupportedIncludes: tx-power
SupportedIncludes: appearance
SupportedIncludes: local-name
SupportedSecondaryChannels: 1M
SupportedSecondaryChannels: 2M
SupportedSecondaryChannels: Coded
The current kernel:
5.9.8-2-MANJARO
Version of bluetoothctl:
bluetoothctl: 5.55
output of "lsmod | grep bluetooth":
bluetooth 737280 12 btrtl,btintel,btbcm,bnep,btusb
ecdh_generic 16384 1 bluetooth
rfkill 28672 9 hp_wmi,bluetooth,cfg80211
crc16 16384 2 bluetooth,ext4
System info:
Kernel: 5.9.8-2-MANJARO x86_64 bits: 64 compiler: gcc v: 10.2.0 Desktop: KDE
Plasma 5.20.3 tk: Qt 5.15.1 wm: kwin_x11 dm: SDDM Distro: Manjaro Linux
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2020-11-20 7:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-20 7:06 bugzilla-daemon [this message]
2020-11-21 19:05 ` [Bug 210275] Bluetooth stopped working on kernel 5.9 bugzilla-daemon
2020-11-23 20:12 ` bugzilla-daemon
2020-11-25 14:14 ` bugzilla-daemon
2020-11-28 19:32 ` bugzilla-daemon
2020-12-09 19:44 ` bugzilla-daemon
2020-12-09 20:25 ` 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-210275-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.