New issue
Advanced search Search tips

Issue 783086 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Nov 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Bluetooth times out, devices are disconnected, reboot is required to get them working again.

Reported by andrewrc...@gmail.com, Nov 9 2017

Issue description

UserAgent: Mozilla/5.0 (X11; CrOS x86_64 9765.85.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.123 Safari/537.36
Platform: 9765.85.0 (Official Build) stable-channel cave

Steps to reproduce the problem:
1. Bluetooth keyboard and mouse connected and working.
2. Leave the machine on but unused for a period of time
3. Try and use keyboard and mouse again, but they no longer work

What is the expected behavior?
Bluetooth keyboard and mouse to stay connected and working after not using the machine for a while.

What went wrong?
Asus C302

Version 61.0.3163.123 (Official Build) (64-bit)

After not using the machine for a while, sometimes an hour, sometimes several hours, the attached bluetooth keyboard and mouse no longer function even though from the chrome settings they appear to be connected.  They keyboard bluetooth light flashes, indicating it's not connected.  

I've done some basic troubleshooting below - this sequence of events happens every time.

dmesg shows a bluetooth timeout:

[39574.854003] SELinux: initialized (dev proc, type proc), uses genfs_contexts
[39603.102765] Bluetooth: hci0 link tx timeout
[39603.102789] Bluetooth: hci0 killing stalled connection 00:1f:20:a8:bd:73
[39676.066468] usb 1-1: USB disconnect, device number 2
[39690.587538] SELinux: initialized (dev proc, type proc), uses genfs_contexts
[39699.539206] SELinux: initialized (dev proc, type proc), uses genfs_contexts
[39706.134911] PDLOG 2017/11/09 08:11:48.1510215107 P1 Disconnected
[39723.190457] Bluetooth: hci0 command 0x200c tx timeout
[39748.800812] SELinux: initialized (dev proc, type proc), uses genfs_contexts
[39874.745990] SELinux: initialized (dev proc, type proc), uses genfs_contexts
[39874.854106] SELinux: initialized (dev proc, type proc), uses genfs_contexts

In bt_console, the controller is still there and the devices still appear to be attached - but they (the devices) are not connected or working

[Dell BT Mouse]# show
Controller 88:78:73:C0:81:CB
        Name: BlueZ 5.44
        Alias: Chromebook_1F8A
        Class: 0x480104
        Powered: yes
        Discoverable: no
        Pairable: yes
        UUID: Headset AG                (00001112-0000-1000-8000-00805f9b34fb)
        UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
        UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
        UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
        UUID: Audio Source              (0000110a-0000-1000-8000-00805f9b34fb)
        UUID: Handsfree Audio Gateway   (0000111f-0000-1000-8000-00805f9b34fb)
        Modalias: bluetooth:v00E0p2452d0400
        Discovering: yes

[Dell BT Mouse]# devices
Device 00:07:61:4E:6C:38 Dell BT Mouse
Device 00:1F:20:A8:BD:73 Logitech K810

So I Turn bluetooth off via chrome settings

bt_console:

[CHG] Device 00:1F:20:A8:BD:73 Connected: no
[CHG] Device 00:07:61:4E:6C:38 Connected: no
[CHG] Controller 88:78:73:C0:81:CB Powered: no
[CHG] Controller 88:78:73:C0:81:CB Discovering: no
[CHG] Controller 88:78:73:C0:81:CB Class: 0x000000

And then turn bluetooth back on via chrome settings:

bt_console:

[DEL] Device 00:1F:20:A8:BD:73 Logitech K810
[DEL] Device 00:07:61:4E:6C:38 Dell BT Mouse
[DEL] Controller 88:78:73:C0:81:CB Chromebook_1F8A [default]

But still nothing works and the controller no longer appears.  I then Turn bluetooth off again via chrome settings, and now I cannot turn bluetooth back on - it just stays greyed out. There is no controller and dmesg shows the same bluetooth timeout.

bt_console:

[bluetooth]# show
No default controller available
[bluetooth]# devices
No default controller available

Dmesg:
[40174.890543] SELinux: initialized (dev proc, type proc), uses genfs_contexts
[40203.105706] Bluetooth: hci0 link tx timeout
[40203.105733] Bluetooth: hci0 killing stalled connection 00:1f:20:a8:bd:73
[40355.182208] SELinux: initialized (dev proc, type proc), uses genfs_contexts
[40358.871658] SELinux: initialized (dev proc, type proc), uses genfs_contexts

To get everything working again, I have to reboot and it all works fine from then on.

bt_console
[NEW] Controller 88:78:73:C0:81:CB Chromebook_1F8A [default]
[NEW] Device 00:07:61:4E:6C:38 Dell BT Mouse
[NEW] Device 00:1F:20:A8:BD:73 Logitech K810
[bluetooth]# show
Controller 88:78:73:C0:81:CB
        Name: BlueZ 5.44
        Alias: Chromebook_1F8A
        Class: 0x000000
        Powered: no
        Discoverable: no
        Pairable: yes
        UUID: Headset AG                (00001112-0000-1000-8000-00805f9b34fb)
        UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
        UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
        UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
        UUID: Audio Source              (0000110a-0000-1000-8000-00805f9b34fb)
        UUID: Handsfree Audio Gateway   (0000111f-0000-1000-8000-00805f9b34fb)
        Modalias: bluetooth:v00E0p2452d0400
        Discovering: no

[CHG] Controller 88:78:73:C0:81:CB Class: 0x480104
[CHG] Controller 88:78:73:C0:81:CB Powered: yes
[CHG] Controller 88:78:73:C0:81:CB Discovering: yes
[CHG] Device 00:07:61:4E:6C:38 Connected: yes
[NEW] Device 54:60:09:E4:B6:23 54-60-09-E4-B6-23
[CHG] Device 54:60:09:E4:B6:23 RSSI: -86
[NEW] Device 48:D6:D5:E1:B1:3A 48-D6-D5-E1-B1-3A
[NEW] Device A4:77:33:D1:35:3F A4-77-33-D1-35-3F
[CHG] Device 54:60:09:E4:B6:23 RSSI: -79
[CHG] Device A4:77:33:D1:35:3F RSSI: -87
[NEW] Device A4:77:33:1F:63:7F A4-77-33-1F-63-7F

dmesg:

[   68.670646] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[   68.670698] Bluetooth: HIDP socket layer initialized
[   68.673332] hid-generic 0005:046D:B004.0001: unknown main item tag 0x0
[   68.673795] input: Dell BT Mouse as /devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:256:1/0005:046D:B004.0001/input/input11
[   68.674589] hid-generic 0005:046D:B004.0001: input,hidraw0: BLUETOOTH HID v82.16 Mouse [Dell BT Mouse] on 88:78:73:c0:81:cb
[   73.367360] SELinux: initialized (dev proc, type proc), uses genfs_contexts
[   80.084928] SELinux: initialized (dev proc, type proc), uses genfs_contexts
[   92.310381] SELinux: initialized (dev proc, type proc), uses genfs_contexts
[   92.399003] audit: type=1400 audit(1510216822.077:88): avc:  denied  { read } for  pid=4949 comm="Binder:1076_3" name="/" dev="tmpfs" ino=17287 scontext=u:r:priv_app:s0:c512,c768 tcontext=u:object_r:device:s0 tclass=dir permissive=0
[   92.482884] audit: type=1400 audit(1510216822.161:89): avc:  denied  { search } for  pid=4949 comm="Binder:1076_3" name="26" dev="proc" ino=24150 scontext=u:r:priv_app:s0:c512,c768 tcontext=u:r:zygote:s0 tclass=dir permissive=0
[  105.829388] SELinux: initialized (dev proc, type proc), uses genfs_contexts
[  108.990310] SELinux: initialized (dev proc, type proc), uses genfs_contexts
[  132.993745] SELinux: initialized (dev proc, type proc), uses genfs_contexts
[  141.576652] hid-generic 0005:046D:B319.0002: unknown main item tag 0x0
[  141.656811] input: Logitech K810 as /devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:512:2/0005:046D:B319.0002/input/input12
[  141.658300] hid-generic 0005:046D:B319.0002: input,hidraw1: BLUETOOTH HID v12.02 Keyboard [Logitech K810] on 88:78:73:c0:81:cb

Did this work before? N/A 

Chrome version: 61.0.3163.123  Channel: stable
OS Version: 9765.85.0
Flash Version: Shockwave Flash 27.0 r0
 
Components: OS>Systems>Bluetooth
Just found this which is very very similar: https://bugs.chromium.org/p/chromium/issues/detail?id=655425
Status: WontFix (was: Unconfirmed)
Issue being tracked here: b/64035404
Issue seems to be resolved now on 62.0.3202.82 Official

Sign in to add a comment