From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 203429] New: RTL8822BE (USB id 13d3:3526) rfkill unblock fails 1 out of 3 attempts
Date: Fri, 26 Apr 2019 08:34:24 +0000 [thread overview]
Message-ID: <bug-203429-62941@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=203429
Bug ID: 203429
Summary: RTL8822BE (USB id 13d3:3526) rfkill unblock fails 1
out of 3 attempts
Product: Drivers
Version: 2.5
Kernel Version: 5.0.0
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Bluetooth
Assignee: linux-bluetooth@vger.kernel.org
Reporter: jprvita@gmail.com
Regression: No
Created attachment 282539
--> https://bugzilla.kernel.org/attachment.cgi?id=282539&action=edit
btmon logs
When rfkill un-blocking this controller using the Bluetooth settings panel on
gnome-control-center, about 1 out of 3 attempts fail. We can see in the kernel
logs (with dynamic debug enabled) and in btmon that a HCI reset is getting a
timeout.
Interestingly, the problem is only reproducible if there was a LE scanning
procedure running before the rfkill switch was blocked. So blocking and
unblocking the adapter in a loop like the one bellow does not hit the problem:
while true ; do echo 1 > /sys/class/rfkill/rfkill2/soft ; sleep 1 ; do echo 0
> /sys/class/rfkill/rfkill2/soft ; sleep 3 ; done
But if I also run another loop in parallel trying to start a LE scan (which
fails most of the time because the adapter is OFF, but things align and a scan
starts quite a few times), the problem reproduces very easily:
while true ; do btmgmt find -l ; done
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2019-04-26 8:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-26 8:34 bugzilla-daemon [this message]
2019-04-26 8:34 ` [Bug 203429] RTL8822BE (USB id 13d3:3526) rfkill unblock fails 1 out of 3 attempts 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-203429-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.