Bug 198803 - Intel Bluetooth 8087:07dc on-board device disconnects from USB bus intermittently
Summary: Intel Bluetooth 8087:07dc on-board device disconnects from USB bus intermitte...
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: Bluetooth (show other bugs)
Hardware: Intel Linux
: P1 normal
Assignee: linux-bluetooth@vger.kernel.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-02-16 10:56 UTC by Dominik Mierzejewski
Modified: 2018-02-16 11:06 UTC (History)
0 users

See Also:
Kernel Version: 4.14.18-300.fc27.x86_64
Subsystem:
Regression: No
Bisected commit-id:

Attachments
dmesg (59.99 KB, text/plain)
2018-02-16 10:56 UTC, Dominik Mierzejewski 		Details
lsusb output (10.17 KB, text/plain)
2018-02-16 11:06 UTC, Dominik Mierzejewski 		Details
Add an attachment (proposed patch, testcase, etc.)

Description Dominik Mierzejewski 2018-02-16 10:56:20 UTC 
Created attachment 274205 [details]
dmesg

The on-board Bluetooth adapter in my laptop intermittently disconnects from USB bus. The following can be seen in dmesg:
[287700.401545] usb 2-6: USB disconnect, device number 92
[287700.406679] Bluetooth: hci0 setting interface failed (19)
[287700.655490] usb 2-6: new full-speed USB device number 34 using xhci_hcd
[287700.782407] usb 2-6: New USB device found, idVendor=8087, idProduct=07dc
[287700.782412] usb 2-6: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[287700.796715] Bluetooth: hci0: read Intel version: 370710018002030d56
[287700.796716] Bluetooth: hci0: Intel device is already patched. patch num: 56
[287721.158617] input: 00:02:3C:65:DD:EC as /devices/virtual/input/input71
[287986.962814] Bluetooth: hci0 SCO packet for unknown connection handle 0
[287986.962818] Bluetooth: hci0 SCO packet for unknown connection handle 0
[292278.831639] usb 2-6: USB disconnect, device number 34

I'm unable to reliably trigger this, but it happens a couple of times a day.
Comment 1 Dominik Mierzejewski 2018-02-16 11:06:00 UTC 
Created attachment 274207 [details]
lsusb output
Note You need to log in before you can comment on or make changes to this bug.