Hi Tore, On Sat, Feb 20, 2016, Tore Anderson wrote: > I uploaded debug files to http://filebin.net/pfmb8043cx : Thanks. > - kernel-debug-messages.$KVER.txt: kernel output (journalctl -k), after > having written "module bluetooth +p" to > the /sys/kernel/debug/dynamic_debug/control file. These are unfortunately not very useful without function information since most functions log very similar things. Could you do +pf instead of +p and try to get these again? To avoid any unnecessary noise, start the logs right before suspending and stop them right after resuming (I hope this is how the other logs were taken). > > Another thing to try in addition to disabling blueman: Add > > AutoEnable=true under the [Policy] section > > in /etc/bluetooth/main.conf. It might make a difference assuming that > > your Bluetooth adapter gets detached and reattached to the USB bus > > when you suspend/resume. > > This made no difference. Note that I had to create that file and its > containing directory anew, it didn't already exist on my Fedora 23 > system. You could have also used src/main.conf from the BlueZ tree as a starting point and removed the '#' from the AutoEnable line: https://git.kernel.org/cgit/bluetooth/bluez.git/plain/src/main.conf Are you sure that you restarted bluetoothd after this change? And you've got a BlueZ version greater than 5.35 (where the feature was introduced)? Johan -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
