https://bugzilla.kernel.org/show_bug.cgi?id=189641 --- Comment #17 from dflogeras2@xxxxxxxxx --- Created attachment 247451 --> https://bugzilla.kernel.org/attachment.cgi?id=247451&action=edit syslog events around bluetooth log up I have not yet chased down the KDE bug I mentioned. However I think it is unrelated, for the last several days I have been testing with a new (clean) user account which bluetooth always starts powered up after a resume, and I am still seeing the bluetooth lockup bug. I'm attaching a system log dump from system resume this morning. Here are some highlights: Dec 12 07:28:19 myhostname kernel: usb 2-6:1.0: rebind failed: -517 Dec 12 07:28:19 myhostname kernel: usb 2-6:1.1: rebind failed: -517 I'm not sure what this means, but usb 2-6 is my 7260 bluetooth device. At 07:28:41 my networking is up, VPN connected, and bluetooth mouse turned on and working. A few minutes later (07:33:02) the BT controller gets reset without any user intervention that I am aware of, I was just clearing emails. After this, you can see at 07:33:21 the USB disconnect, which is a direct result from me issuing a "rfkill block" / "rfkill unblock" to manually toggle the device. -- You are receiving this mail because: You are the assignee for the bug. -- 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
