Unrecoverable advertisement/discovery errors on Kevin |
|||
Issue descriptionKevin: CrOS 10446.0.0, Chrome 66.0.3357.0 I left an Instant Tethering scan w/ 4 devices active. Eventually it hits an unending stream of BLE advertisement and BLE discovery errors. Note that Kevin does NOT use an Intel chip for Bluetooth, so this is not b/69529500. Kevin chip info (via go/crconn): Marvell MVL 8997 Marvell 8997 Azurewave
,
Feb 28 2018
Dmitry could you take a look at this?
,
Apr 2 2018
Hi Dmitry - friendly ping :). Do you think you can get this issue triaged? If this is a firmware issue, I'd like to reach out to Marvell ASAP to get their team on it. Our other firmware issues have taken a long time to get done, so I'd like to get a head start on this issue.
,
Apr 2 2018
I could help take a look today. It seems to me that it is the controller issue. Will post more details later.
,
Apr 3 2018
This is the underlying controller/firmware issue. I think we need to have Marvell take a look ASAP.
--- more details below ---
There were continuous "tx timeout" errors starting at
2018-02-28T14:54:16.098908-08:00 ERR kernel: [ 501.388865] Bluetooth: hci_core.c:hci_cmd_timeout() hci0 command 0x2016 tx timeout
Looking at the btsnoop log, the "Set Advertising Data" HCI command never got a reply from the underlying controller.
< HCI Command: LE Set Advertising Data (0x08|0x0008) plen 32 #42340 [hci0] 2018-03-01 06:54:16.098016
Length: 13
16-bit Service UUIDs (complete): 1 entry
Google Inc. (0xfe50)
Service Data (UUID 0xfe50): 01268fc301
After 2-second timeout, kernel tried again and again to resend the command. The controller failed to respond thereafter.
,
Apr 4 2018
Removing RVG. |
|||
►
Sign in to add a comment |
|||
Comment 1 by khorimoto@chromium.org
, Feb 28 20184.6 MB
4.6 MB Download