bluetooth pára de funcionar - “Falha ao ligar: org.bluez.Error.Failed”

7

Descrição do erro

Eu quero usar meu mouse bluetooth. Simples assim. então eu conectei o mouse com o meu notebook - no começo ele funcionava bem, mas depois de vários minutos ele de repente parou de funcionar e ele não irá iniciar até a reinicialização.

então eu reiniciei meu notebook, e no início do sistema tudo funciona bem, mas novamente depois de alguns minutos meu mouse pára de funcionar.

informações úteis

informação geral

OS: Ubuntu 17.04 x86_64 
Model: W840SU Series 
Kernel: 4.10.0-21-generic 
DE: Budgie 
WM: Mutter(Budgie) 
CPU: Intel i5-4200U (4) @ 2.6GHz 
GPU: Intel Haswell Mobile 
Memory: 3500MiB / 7870MiB 

lsusb ::

Bus 001 Device 002: ID 8087:8000 Intel Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 004: ID 5986:0536 Acer, Inc 
Bus 002 Device 003: ID 8087:07dc Intel Corp. 
Bus 002 Device 002: ID 0eef:a122 D-WAV Scientific Co., Ltd 
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root

logo após o início do sistema:

saída de hciconfig, bluetoothctl e rfkill

logo após o mouse parar de funcionar

saída de hciconfig, bluetoothctl e rfkill

saída de syslog

dmesg | grep Blue
[    5.049999] Bluetooth: Core ver 2.22
[    5.050029] Bluetooth: HCI device and connection manager initialized
[    5.050032] Bluetooth: HCI socket layer initialized
[    5.050034] Bluetooth: L2CAP socket layer initialized
[    5.050041] Bluetooth: SCO socket layer initialized
[    5.202899] Bluetooth: hci0: read Intel version: 370710010002030d56
[    5.202900] Bluetooth: hci0: Intel device is already patched. patch num: 56
[    5.209461] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    5.209463] Bluetooth: BNEP filters: protocol multicast
[    5.209468] Bluetooth: BNEP socket layer initialized
[   29.802314] Bluetooth: RFCOMM TTY layer initialized
[   29.802320] Bluetooth: RFCOMM socket layer initialized
[   29.802325] Bluetooth: RFCOMM ver 1.11
[   33.640917] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[   33.640923] Bluetooth: HIDP socket layer initialized
[   33.648277] input: Bluetooth Mouse M557 as /devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5:1.0/bluetooth/hci0/hci0:256/0005:046D:B010.0002/input/input24
[   33.651568] hid-generic 0005:046D:B010.0002: input,hidraw1: BLUETOOTH HID v10.01 Mouse [Bluetooth Mouse M557] on a0:88:69:15:35:82
[  998.091592] Bluetooth: hci0 command 0x0804 tx timeout
[ 1010.060391] Bluetooth: hci0 command 0x0c14 tx timeout
[ 1292.746097] Bluetooth: hci0 command 0x0406 tx timeout
[ 1297.962695] Bluetooth: hci0 command 0xfc3f tx timeout
[ 1303.211103] Bluetooth: hci0 command 0x0c52 tx timeout
[ 1305.227339] Bluetooth: hci0 command 0x0c13 tx timeout
[ 1306.187346] Bluetooth: hci0: turning off Intel device LED failed (-110)
[ 1528.198244] Bluetooth: hci0 urb ffff9be87115af00 failed to resubmit (113)
[ 1539.090928] Bluetooth: hci0 urb ffff9be94d2df9c0 failed to resubmit (113)
[ 1548.147837] Bluetooth: hci0 urb ffff9be94d2df9c0 failed to resubmit (113)
[ 1559.176769] Bluetooth: hci0 urb ffff9be94ef6c6c0 failed to resubmit (113)
[ 1780.029401] Bluetooth: hci0 urb ffff9be94f8b96c0 failed to resubmit (113)
[ 2167.226568] Bluetooth: hci0 urb ffff9be7b54c7900 failed to resubmit (113)
[ 2207.166935] Bluetooth: hci0 urb ffff9be88efea480 failed to resubmit (113)
[ 2483.163077] Bluetooth: hci0 urb ffff9be79f86f3c0 failed to resubmit (113)
[ 2493.148010] Bluetooth: hci0 urb ffff9be8d338a540 failed to resubmit (113)
[ 4388.304302] Bluetooth: hci0 urb ffff9be76b0f89c0 failed to resubmit (113)

essa pode ser a parte interessante:

[bluetooth]# power on
Failed to set power on: org.bluez.Error.Failed
    
por Soraphis 17.05.2017 / 11:11

2 respostas

1

Tentando usar meu teclado Bluetooth Logitech K380, tive os mesmos problemas que Soraphis. A desinstalação do TLP do meu sistema acabou resolvendo isso para mim.

Tente desativar ou desinstalar o TLP se você o tiver instalado.

    
por Murmel 05.10.2017 / 06:40
0

Como não pode alcançar o hci0:

hciconfig hci0 up

poderia fazer o truque.

    
por ADDB 17.05.2017 / 11:26