I was able to reproduce this  issue 100 % time when restarting Chrome with [Esc] + [F3] + [Power] pressed keys.

Then, here's what I can see in my dmesg logs:

[Fri Dec 16 13:38:44 2016] usb 1-1.2: USB disconnect, device number 5

[Fri Dec 16 13:38:44 2016] usb 1-1.2: new full-speed USB device number 6 using ehci-pci
[Fri Dec 16 13:38:44 2016] usb 1-1.2: string descriptor 0 read error: -22
[Fri Dec 16 13:38:44 2016] usb 1-1.2: New USB device found, idVendor=0489, idProduct=e057
[Fri Dec 16 13:38:44 2016] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3

[Fri Dec 16 13:38:44 2016] usb 1-1.2: USB disconnect, device number 6

[Fri Dec 16 13:38:44 2016] usb 1-1.2: new full-speed USB device number 7 using ehci-pci
[Fri Dec 16 13:38:44 2016] usb 1-1.2: string descriptor 0 read error: -22
[Fri Dec 16 13:38:44 2016] usb 1-1.2: New USB device found, idVendor=0489, idProduct=e057
[Fri Dec 16 13:38:44 2016] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3

[Fri Dec 16 13:38:47 2016] input: MX Master as /devices/virtual/misc/uhid/input15
[Fri Dec 16 13:38:47 2016] cpufreq_interactive: monitoring input on MX Master
[Fri Dec 16 13:38:47 2016] hid-generic 0005:046D:B012.0002: input,hidraw0: BLUETOOTH HID v0.14 Keyboard [MX Master] on A4:17:31:78:A6:04

And here's what says lsusb:

Bus 001 Device 007: ID 0489:e057 Foxconn / Hon Hai 
Bus 001 Device 003: ID 2232:1033 Silicon Motion 
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


This is a crash happening in "Foxconn / Hon Hai" device and we should fix it.

And here's what happened in /var/log/messages at the same time:

2016-12-16T13:38:44.598887+01:00 INFO kernel: [   61.078312] usb 1-1.2: USB disconnect, device number 5
2016-12-16T13:38:44.617064+01:00 ERR bluetoothd[1634]: Wrong size of start discovery return parameters
2016-12-16T13:38:44.641894+01:00 INFO bluetoothd[1634]: Endpoint unregistered: sender=:1.24 path=/org/chromium/Cras/Bluetooth/A2DPSource
2016-12-16T13:38:44.642636+01:00 NOTICE dbus[512]: [system] Rejected send message, 3 matched rules; type="method_return", sender=":1.24" (uid=600 pid=1627 comm="/usr/bin/cras ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.25" (uid=218 pid=1634 comm="/usr/libexec/bluetooth/bluetoothd --nodetach ")
2016-12-16T13:38:44.802865+01:00 INFO kernel: [   61.281763] usb 1-1.2: new full-speed USB device number 6 using ehci-pci
2016-12-16T13:38:44.889911+01:00 ERR kernel: [   61.369013] usb 1-1.2: string descriptor 0 read error: -22
2016-12-16T13:38:44.889975+01:00 INFO kernel: [   61.369044] usb 1-1.2: New USB device found, idVendor=0489, idProduct=e057
2016-12-16T13:38:44.889989+01:00 INFO kernel: [   61.369064] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
2016-12-16T13:38:44.642723+01:00 NOTICE dbus[512]: [system] Rejected send message, 3 matched rules; type="method_return", sender=":1.24" (uid=600 pid=1627 comm="/usr/bin/cras ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.25" (uid=218 pid=1634 comm="/usr/libexec/bluetooth/bluetoothd --nodetach ")
2016-12-16T13:38:45.110861+01:00 INFO kernel: [   61.589645] usb 1-1.2: new full-speed USB device number 7 using ehci-pci
2016-12-16T13:38:45.198902+01:00 ERR kernel: [   61.678025] usb 1-1.2: string descriptor 0 read error: -22
2016-12-16T13:38:45.198964+01:00 INFO kernel: [   61.678081] usb 1-1.2: New USB device found, idVendor=0489, idProduct=e057
2016-12-16T13:38:45.198976+01:00 INFO kernel: [   61.678115] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
2016-12-16T13:38:45.368301+01:00 INFO bluetoothd[1634]: Endpoint registered: sender=:1.24 path=/org/chromium/Cras/Bluetooth/A2DPSource
2016-12-16T13:38:45.368744+01:00 INFO bluetoothd[1634]: Player registered: sender=:1.24 path=/org/chromium/Cras/Bluetooth/DefaultPlayer
2016-12-16T13:38:45.368924+01:00 ERR cras_server[1627]: RegisterProfile returned error: org.bluez.Error.AlreadyExists
2016-12-16T13:38:47.587917+01:00 INFO kernel: [   64.065829] input: MX Master as /devices/virtual/misc/uhid/input15
2016-12-16T13:38:47.588041+01:00 INFO kernel: [   64.066263] cpufreq_interactive: monitoring input on MX Master
2016-12-16T13:38:47.588059+01:00 INFO kernel: [   64.066539] hid-generic 0005:046D:B012.0002: input,hidraw0: BLUETOOTH HID v0.14 Keyboard [MX Master] on A4:17:31:78:A6:04

Hi François, what is the chromebook model?
Could you attach the /var/log/messages file too? Thanks.

BTW, when I press ESC + F3 + POWER, I would get "Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card". What did you do from here?

Content of /var/log/messages is in comment #2. Here's attached the full file from what I've just reproduced few minutes ago. For info, Bluetooth turned OFF by itself at 2016-12-23T08:57:44.840819+01:00

My chromebook is in Developer Mode to be able to run [Crouton](https://github.com/dnschneid/crouton). From there, I simply pressed <Ctrl> + D to continue.

Let me know if you need more logs.

Deleted: messages.txt 3.3 MB

messages.txt 3.3 MB View Download

It looks like it is the same issue as 678692.

It looks very similar to  Issue 678692  as the the problems were caused by "USB disconnect". In  Issue 678692 , the chromebook model is samus and bt chip is made by Intel. Intel is looking into the issue. 

For Link here, it uses QC Atheros's chip. Let's keep these two issues separate for a while and see what problems Intel could find.

I've been playing a lot in 2016 with Bluetooth on this very Link device and it's the first time I see something like that. Do you know if there has been a firmware update?

Could https://bugzilla.kernel.org/show_bug.cgi?id=190831 be related as well?

Re C#11: the bugzilla issue mentioned might be related. However, I am not sure.

I tended to consider the issue is related with hardware/firmware because I am not able to reproduce the problem on  Issue 678692  on my own samus machine. But this issue is found on a Link machine. 

(1) Are you able to reproduce the issue on the same Link machine with a different model of BLE peripheral in addition to MX Master mouse?

I was able to reproduce with PLAYBULB Candle BLE device in addition to MX Master mouse.

(2) Are you able to reproduce the issue on the same Link machine with a classic bluetooth peripheral?

I don't have a classic bluetooth peripheral to test with now.

(3) Are you able to reproduce the problem on a different model of chromebook with the same MX Master mouse and the same version of chrome-os image?

I'm not sure how to do that.

(4) If you happen to have a different Link machine, are you able to reproduce the problem with the same MX Master mouse and the same version of chrome-os image?

I've borrowed Link machine from a coworker and I can reproduce the issue with the same MX Master mouse.
I believe* this is the same chrome-os image according to about:system

Hi François, thank you for the information in Comment#13. It seems to me that there is something unusual about BLE in the bt controller which causes the USB disconnection.

This problem is very similar to  Issue 678692 . Recently, I am able to reproduce the problem on my Samus too. Intel has provided a new fw and I am verifying it.

Would you please help create a partner issue and assign the issue to QC for them to look into? Thank you very much!

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot