https://bugzilla.kernel.org/show_bug.cgi?id=207629 --- Comment #9 from Abhishek Pandit-Subedi (abhishekpandit@xxxxxxxxxxxx) --- 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.
