New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 678037 link

Starred by 1 user
Status: Assigned
Owner:
█ mcchou@chromium.org
Last visit > 30 days ago
Cc:
josephsih@chromium.org
snanda@chromium.org
█ djkurtz@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug

Blocked on:
issue chrome-os-partner:61480


Sign in to add a comment

Elm: MX Master mouse frequently stops working

Project Member Reported by mcchou@chromium.org, Jan 3 2017 
Description:
Purchased Acer R13 Chromebook a few days ago.  While using an MX Master mouse, it frequently stops working.  I check the bluetooth status, and it appears to be Enabled.  When I click disable blue tooth, it disables it, but then when trying to re-enable the bluetooth it doesn't work.  I click on Enable bluetooth, and nothing happens, I click on the bluetooth symbol and nothing happens, I click on Manage Devices, then check Enable Bluetooth (the check mark appears, but nothing happens). It happens 5-6 times a day, usually restarting the computer will fix it, but this is getting annoying.

UI language:
en-US

Version:
55.0.2883.103

Product Specific Data (whitelisted):
CHROME VERSION: 55.0.2883.103
CHROMEOS_AUSERVER: <URL: 1>
CHROMEOS_RELEASE_BOARD: elm-signed-mpkeys
CHROMEOS_RELEASE_DESCRIPTION: 8872.73.0 (Official Build) stable-channel elm
CHROMEOS_RELEASE_TRACK: stable-channel
CHROMEOS_RELEASE_VERSION: 8872.73.0
ENTERPRISE_ENROLLED: Not managed
expi:  3300110 3300134 3312591 3312807 3313274 3313321
hardware_class: ELM D4A-A2A-G5A-A62

Browser:
Chrome 55.0.2883.103

Java Enabled:
false

OS:
CrOS aarch64 8872.73.0

URL:
chrome://settings/search#Bluetooth

Product ID:
208

Bucket ID:
8589935399

Comment 1 by mcchou@chromium.org, Jan 3 2017 

Kernel log from  djkurtz@:

This one may be device specific, as there seems to be many bluetooth related messages in the kernel log:

2016-12-31 17:57:05.065 3 kernel  :  [ 5382.639923] Bluetooth: sdio_readsb: read int hw_regs failed: -110
2016-12-31 17:57:05.065 3 kernel  :  [ 5382.639960] Bluetooth: read int hw_regs 2nd attempt also failed: -110

2016-12-31T16:53:53.839680-05:00 INFO kernel: [ 3084.261316] mwifiex_sdio mmc2:0001:1: event: unknown event id: 0x74
2016-12-31T16:54:43.387681-05:00 INFO kernel: [ 3133.809799] mwifiex_sdio mmc2:0001:1: BA setup with unknown TDLS peer ff:ff:ff:00:00:04!
2016-12-31T16:58:53.843664-05:00 INFO kernel: [ 3384.267301] mwifiex_sdio mmc2:0001:1: event: unknown event id: 0x74
2016-12-31T17:01:36.851555-05:00 ERR kernel: [ 3547.273167] Bluetooth: readsb failed: -110
2016-12-31T17:01:46.195604-05:00 INFO kernel: [ 3556.618713] mwifiex_sdio mmc2:0001:1: BA setup with unknown TDLS peer ff:ff:ff:00:00:04!
2016-12-31T17:06:43.611572-05:00 ERR kernel: [ 3854.032086] Bluetooth: read rx_len failed
2016-12-31T17:08:53.847702-05:00 INFO kernel: [ 3984.270560] mwifiex_sdio mmc2:0001:1: event: unknown event id: 0x74
2016-12-31T17:12:25.335787-05:00 INFO kernel: [ 4195.755757] mwifiex_sdio mmc2:0001:1: BA setup with unknown TDLS peer ff:ff:ff:00:00:04!

// suspend & resume

2016-12-31T17:57:05.065564-05:00 ERR kernel: [ 5382.639923] Bluetooth: sdio_readsb: read int hw_regs failed: -110
2016-12-31T17:57:05.065600-05:00 ERR kernel: [ 5382.639960] Bluetooth: read int hw_regs 2nd attempt also failed: -110
2016-12-31T17:58:36.445597-05:00 ERR kernel: [ 5474.019642] Bluetooth: hci0 command 0x2005 tx timeout
2016-12-31T17:58:38.449592-05:00 ERR kernel: [ 5476.023658] Bluetooth: hci0 command 0x200b tx timeout
2016-12-31T17:58:40.453578-05:00 ERR kernel: [ 5478.027648] Bluetooth: hci0 command 0x200c tx timeout
2016-12-31T17:58:48.453673-05:00 ERR kernel: [ 5486.027621] Bluetooth: hci0 command 0x2005 tx timeout
2016-12-31T17:58:50.457759-05:00 ERR kernel: [ 5488.031772] Bluetooth: hci0 command 0x200b tx timeout
2016-12-31T17:58:52.461573-05:00 ERR kernel: [ 5490.035758] Bluetooth: hci0 command 0x200c tx timeout
2016-12-31T17:59:00.453660-05:00 ERR kernel: [ 5498.027778] Bluetooth: hci0 command 0x2005 tx timeout
2016-12-31T17:59:02.456338-05:00 ERR kernel: [ 5500.031763] Bluetooth: hci0 command 0x200b tx timeout
2016-12-31T17:59:04.461789-05:00 ERR kernel: [ 5502.035758] Bluetooth: hci0 command 0x200c tx timeout
2016-12-31T17:59:10.677738-05:00 INFO kernel: [ 5508.254040] mwifiex_sdio mmc2:0001:1: event: unknown event id: 0x74
2016-12-31T17:59:12.445574-05:00 ERR kernel: [ 5510.019650] Bluetooth: hci0 command 0x2005 tx timeout
2016-12-31T17:59:14.449605-05:00 ERR kernel: [ 5512.023639] Bluetooth: hci0 command 0x200b tx timeout
2016-12-31T17:59:16.453591-05:00 ERR kernel: [ 5514.027636] Bluetooth: hci0 command 0x200c tx timeout
2016-12-31T17:59:24.453669-05:00 ERR kernel: [ 5522.028237] Bluetooth: hci0 command 0x2005 tx timeout
2016-12-31T17:59:26.457587-05:00 ERR kernel: [ 5524.031633] Bluetooth: hci0 command 0x200b tx timeout
2016-12-31T17:59:28.461571-05:00 ERR kernel: [ 5526.035633] Bluetooth: hci0 command 0x200c tx timeout
2016-12-31T17:59:36.453569-05:00 ERR kernel: [ 5534.027632] Bluetooth: hci0 command 0x2005 tx timeout
2016-12-31T17:59:38.457655-05:00 ERR kernel: [ 5536.031637] Bluetooth: hci0 command 0x200b tx timeout
2016-12-31T17:59:40.461689-05:00 ERR kernel: [ 5538.035631] Bluetooth: hci0 command 0x200c tx timeout
2016-12-31T17:59:48.453662-05:00 ERR kernel: [ 5546.027640] Bluetooth: hci0 command 0x2005 tx timeout
2016-12-31T17:59:50.457579-05:00 ERR kernel: [ 5548.031765] Bluetooth: hci0 command 0x200b tx timeout
2016-12-31T17:59:52.461590-05:00 ERR kernel: [ 5550.035626] Bluetooth: hci0 command 0x200c tx timeout
2016-12-31T18:00:00.453581-05:00 ERR kernel: [ 5558.027602] Bluetooth: hci0 command 0x2005 tx timeout
2016-12-31T18:00:02.455095-05:00 ERR kernel: [ 5560.031631] Bluetooth: hci0 command 0x200b tx timeout
2016-12-31T18:00:04.461580-05:00 ERR kernel: [ 5562.035950] Bluetooth: hci0 command 0x200c tx timeout
2016-12-31T18:00:12.453540-05:00 ERR kernel: [ 5570.027676] Bluetooth: hci0 command 0x2005 tx timeout
2016-12-31T18:00:14.457739-05:00 ERR kernel: [ 5572.031740] Bluetooth: hci0 command 0x200b tx timeout
2016-12-31T18:00:16.461654-05:00 ERR kernel: [ 5574.035736] Bluetooth: hci0 command 0x200c tx timeout
2016-12-31T18:00:18.609555-05:00 ERR kernel: [ 5576.183655] Bluetooth: hci0 command 0x2005 tx timeout
2016-12-31T18:00:20.613590-05:00 ERR kernel: [ 5578.187644] Bluetooth: hci0 command 0x200b tx timeout
2016-12-31T18:00:22.617703-05:00 ERR kernel: [ 5580.191641] Bluetooth: hci0 command 0x200c tx timeout
2016-12-31T18:00:30.453563-05:00 ERR kernel: [ 5588.027613] Bluetooth: hci0 command 0x2005 tx timeout
2016-12-31T18:00:32.458309-05:00 ERR kernel: [ 5590.035595] Bluetooth: hci0 command 0x200b tx timeout
2016-12-31T18:00:34.465573-05:00 ERR kernel: [ 5592.039594] Bluetooth: hci0 command 0x200c tx timeout

2016-12-31T18:05:44.445592-05:00 ERR kernel: [ 5902.019641] Bluetooth: hci0 command 0x2005 tx timeout
2016-12-31T18:05:46.449577-05:00 ERR kernel: [ 5904.023646] Bluetooth: hci0 command 0x200b tx timeout
2016-12-31T18:05:48.453594-05:00 ERR kernel: [ 5906.027644] Bluetooth: hci0 command 0x200c tx timeout
2016-12-31T18:05:50.457586-05:00 ERR kernel: [ 5908.031611] Bluetooth: hci0 command 0x0406 tx timeout
2016-12-31T18:06:05.509878-05:00 ERR bluetoothd[1737]: Failed to set mode: Failed (0x03)
2016-12-31T18:06:15.510254-05:00 ERR bluetoothd[1737]: Failed to set mode: Failed (0x03)
2016-12-31T18:06:25.509908-05:00 ERR bluetoothd[1737]: Failed to set mode: Failed (0x03)
2016-12-31T18:06:56.381891-05:00 ERR bluetoothd[1737]: last message repeated 2 times

2016-12-31T18:07:06.382245-05:00 ERR bluetoothd[1737]: Failed to set mode: Failed (0x03)
2016-12-31T18:08:23.057923-05:00 ERR bluetoothd[1737]: Failed to set mode: Failed (0x03)
2016-12-31T18:09:27.950246-05:00 ERR bluetoothd[1737]: Failed to set mode: Failed (0x03)
2016-12-31T18:09:42.741783-05:00 ERR bluetoothd[1737]: Failed to set mode: Failed (0x03)

Comment 2 by mcchou@chromium.org, Jan 6 2017

Labels: M-56 Restrict-View-Google

Comment 3 by mcchou@chromium.org, Jan 6 2017

Blockedon: chrome-os-partner:61480

Comment 4 by mcchou@chromium.org, Jan 7 2017

Labels: -Restrict-View-Google

Comment 5 by mcchou@chromium.org, Jan 7 2017 

The link to the feedback in the issue summary:
https://feedback.corp.google.com/#/Report/51013674938
►

Sign in to add a comment