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
Date: Tue, 12 May 2020 22:12:44 +0000 [thread overview]
Message-ID: <bug-207629-62941-GwruxSuro1@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 #9 from Abhishek Pandit-Subedi (abhishekpandit@chromium.org) ---
Could you collect grab dmesg w/ dynamic debug enabled? This will give us some
confirmation about what's going on in Bluetooth (especially since 0x0c1a is
sent before 0x2042 and that should be timing out first).
Dyndebug instructions:
https://www.kernel.org/doc/html/latest/admin-guide/dynamic-debug-howto.html
Please enable debug for files hci_core.c, hci_request.c and hci_event.c:
(for example: echo 'file hci_core.c +p' > <debugfs>/dynamic_debug/control)
Collecting this is probably the most useful observation of this bunch.
--
I'm not familiar with what power hooks Ubuntu uses but it might be worth
checking the systemd-sleep programs to see if any of them are going to rfkill
bluetooth:
https://wiki.archlinux.org/index.php/Power_management#Hooks_in_/usr/lib/systemd/system-sleep
--
You can also try running `rfkill event` in shell while suspending. This might
capture any service that is rfkill-ing without your knowledge.
http://manpages.ubuntu.com/manpages/bionic/man8/rfkill.8.html
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2020-05-12 22:12 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 [this message]
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
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-GwruxSuro1@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).