Citeren Oliver Neukum
Am Samstag, den 02.12.2017, 21:03 +0000 schrieb Foolish Ewe:
You suggested just blacklisting the btusb device.
> USB_BLACKLIST="8087:0a2b"
I had considered trying just the btusb device (as you suggest) approach, but I wanted to stop the failures, I really wanted to stop rebooting to enable bluetooth. If I get good results over a few days, I'll try relaxing that setting.
I cannot send a patch to disable runtime PM for a very common device upstream, unless I am positive it really is the device which causes the issue, as opposed to a wierd interaction of the device and your hub or chip set. So we really need to know whether blacklisting the device alone stops the problems.
I'm not sure what the problem is, but I see similar problems if I don't use either of the below lines in my /etc/default/tlp file USB_BLACKLIST="8087:07dc" or USB_BLACKLIST_BTUSB=1 Which isn't totally surprising, since the above device is the btusb device. A more generic fix may therefor be to default to the second line, blacklisting all btusb devices and advising people to try *not* blacklisting the btusb device in order to save power. It took me quite a while to figure out why my mouse wasn't working properly under Linux, while on the same machine, the same mouse worked well under Windows. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org