From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 207629] BISECTED Bluetooth: hci0: command 0x2042 tx timeout - suspend fails - Dell XPS 9300, Dell XPS 7390, Dell Inspiron 7386, Intel NUC7JYB
Date: Wed, 13 May 2020 23:15:35 +0000 [thread overview]
Message-ID: <bug-207629-62941-ftCXF2tgTY@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-207629-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=207629
--- Comment #17 from Abhishek Pandit-Subedi (abhishekpandit@chromium.org) ---
I found another patch in Chromium repository that seems to work around this
issue. It comes down to conditional cmd execution that is specific to the
passive scanning code. It explains why the issue occurs specifically on the
passive scanning and why it only happens sometimes.
https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/1636009
Could you try this patch and see if it fixes your issue? If yes, I'll try to
get it merged upstream.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2020-05-13 23:15 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-207629-62941@https.bugzilla.kernel.org/>
2020-05-11 3:05 ` [Bug 207629] BISECTED Bluetooth: hci0: command 0x2042 tx timeout - suspend fails - Dell XPS 9300 bugzilla-daemon
2020-05-11 4:06 ` bugzilla-daemon
2020-05-11 4:59 ` bugzilla-daemon
2020-05-11 19:11 ` bugzilla-daemon
2020-05-12 16:00 ` bugzilla-daemon
2020-05-12 22:12 ` bugzilla-daemon
2020-05-13 4:00 ` bugzilla-daemon
2020-05-13 4:11 ` bugzilla-daemon
2020-05-13 4:56 ` bugzilla-daemon
2020-05-13 16:51 ` bugzilla-daemon
2020-05-13 21:55 ` [Bug 207629] BISECTED Bluetooth: hci0: command 0x2042 tx timeout - suspend fails - Dell XPS 9300, Dell XPS 7390, Dell Inspiron 7386, Intel NUC7JYB bugzilla-daemon
2020-05-13 22:59 ` bugzilla-daemon
2020-05-13 23:15 ` bugzilla-daemon [this message]
2020-05-14 1:47 ` bugzilla-daemon
2020-06-03 14:32 ` bugzilla-daemon
2020-06-03 14:37 ` bugzilla-daemon
2020-06-03 16:17 ` bugzilla-daemon
2020-06-04 14:53 ` bugzilla-daemon
2020-06-25 14:47 ` bugzilla-daemon
2020-06-25 14:53 ` bugzilla-daemon
2020-06-26 17:31 ` bugzilla-daemon
2020-07-14 0:20 ` bugzilla-daemon
2020-08-20 13:07 ` bugzilla-daemon
2020-08-20 13:38 ` bugzilla-daemon
2020-08-20 16:59 ` bugzilla-daemon
2020-10-13 14:45 ` bugzilla-daemon
2020-10-13 14:46 ` 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-207629-62941-ftCXF2tgTY@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).