Bug 10628 - Parselogs: Failed to obtain handles for "Service Changed" characteristic
Summary: Parselogs: Failed to obtain handles for "Service Changed" characteristic
Status: RESOLVED FIXED
Alias: None
Product: BSPs
Classification: Build System, Metadata & Runtime
Component: bsps-intel-corei7-64 (show other bugs)
Version: 2.2
Hardware: x86 x86_64
: Medium normal
Target Milestone: 2.4
Assignee: California Sullivan
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2016-11-08 18:29 UTC by Juan Ramos
Modified: 2017-05-18 16:48 UTC (History)
1 user (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
LSB-corei7-64_NUC log (27.80 KB, application/octet-stream)
2016-11-08 18:29 UTC, Juan Ramos 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Juan Ramos 2016-11-08 18:29:40 UTC 
Created attachment 3532 [details]
LSB-corei7-64_NUC log

STATUS: IDLE
BUILD: 2.2 rc6: dc8508f609974cc99606b9042bfa7f870ce80228
ENVIRONMENT: corei7-64-lsb on NUC
STEPS TO REPRODUCE: 
  
 Parse dmesg log and all log files in /var/log for keywords like: "error" , "failed" , "cannot", "can't" etc.
Filter out the known and invalid errors or errors that appear in certain situations and need to be ignored.



EXPECTED OUTCOME: 
  
 No errors or fails should be present in logs

Actual result:

Central error: Nov  7 19:24:55 intel-corei7-64 bluetoothd[1221]: Failed to obtain handles for "Service Changed" characteristic


Central error: Nov  7 19:24:48 intel-corei7-64 kernel: [    9.382358] Bluetooth: hci0: Failed to send firmware data (-38)


Central error: Nov  7 19:25:08 intel-corei7-64 getty[1390]: tcgetattr: Input/output error^M 


Central error: [    9.382358] Bluetooth: hci0: Failed to send firmware data (-38)
Comment 1 California Sullivan 2017-04-19 23:08:15 UTC 
It looks like the NUC6 just has problems bringing up its Bluetooth device that early in the boot sequence, and it retries later. In my case I see:

[    4.091790] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[    4.097326] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
[    4.145317] Bluetooth: hci0: Failed to send firmware data (-38)

Followed by this later on:

[   11.509870] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[   11.509988] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
[   13.090308] Bluetooth: hci0: Waiting for firmware download to complete
[   13.090829] Bluetooth: hci0: Firmware loaded in 1549114 usecs
[   13.090987] Bluetooth: hci0: Waiting for device to boot
[   13.101958] Bluetooth: hci0: Device booted in 10818 usecs

With Bluetooth coming up successfully.

This behavior is consistent with between 4.1 and 4.9 kernels.

I will send a whitelist patch.
Comment 2 California Sullivan 2017-04-21 22:21:16 UTC 
Whitelist patch sent to mailing list.