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

Issue 663284 link

Starred by 1 user
Status: Verified
Owner:
█ mcchou@chromium.org
Last visit > 30 days ago
Closed: Nov 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Remove bluetoothd log errors

Project Member Reported by fbeaufort@chromium.org, Nov 8 2016 
Chrome Version       : 56.0.2905.0
OS Version: 8953.0.0

What steps will reproduce the problem?
1. Turn on Bluetooth
2. Check out file:///var/log/messages

What is the expected result?

It should not contain any Bluetooth errors

What happens instead of that?

2016-11-08T10:16:43.258384+01:00 INFO bluetoothd[14513]: Bluetooth daemon 5.41
2016-11-08T10:16:43.260715+01:00 INFO bluetoothd[14513]: Starting SDP server
2016-11-08T10:16:43.263862+01:00 WARNING bluetoothd[14513]: kernel lacks bnep-protocol support
2016-11-08T10:16:43.263885+01:00 WARNING bluetoothd[14513]: System does not support network plugin
2016-11-08T10:16:43.264950+01:00 ERR bluetoothd[14513]: Failed to open RFKILL control device
2016-11-08T10:16:43.265055+01:00 INFO bluetoothd[14513]: Bluetooth management interface 1.11 initialized
2016-11-08T10:16:43.265269+01:00 ERR bluetoothd[14513]: Failed to obtain handles for "Service Changed" characteristic
2016-11-08T10:16:43.282292+01:00 INFO bluetoothd[14513]: Endpoint registered: sender=:1.28 path=/org/chromium/Cras/Bluetooth/A2DPSource
2016-11-08T10:16:43.284237+01:00 INFO bluetoothd[14513]: Player registered: sender=:1.28 path=/org/chromium/Cras/Bluetooth/DefaultPlayer

Are all these errors expected?
If not, what can we do to clear them out?

And here's what I got when running my custom build of BlueZ (which is not relevant since it uses bootstrap-configure)
2016-11-08T09:08:53.455058+01:00 INFO bluetoothd[2376]: Bluetooth daemon 5.41
2016-11-08T09:08:53.472601+01:00 INFO bluetoothd[2376]: Starting SDP server
2016-11-08T09:08:53.500236+01:00 WARNING bluetoothd[2376]: kernel lacks bnep-protocol support
2016-11-08T09:08:53.500264+01:00 WARNING bluetoothd[2376]: System does not support network plugin
2016-11-08T09:08:53.501561+01:00 ERR bluetoothd[2376]: Failed to open RFKILL control device
2016-11-08T09:08:53.501761+01:00 INFO bluetoothd[2376]: Bluetooth management interface 1.11 initialized
2016-11-08T09:08:53.502155+01:00 ERR bluetoothd[2376]: Failed to obtain handles for "Service Changed" characteristic
2016-11-08T09:08:53.502480+01:00 ERR bluetoothd[2376]: Not enough free handles to register service
2016-11-08T09:08:53.502534+01:00 ERR bluetoothd[2376]: gatt-example-adapter-driver: Input/output error (5)
2016-11-08T09:08:53.502769+01:00 ERR bluetoothd[2376]: Sap driver initialization failed.
2016-11-08T09:08:53.502786+01:00 ERR bluetoothd[2376]: sap-server: Operation not permitted (1)
2016-11-08T09:08:53.608109+01:00 INFO bluetoothd[2376]: Endpoint registered: sender=:1.28 path=/org/chromium/Cras/Bluetooth/A2DPSource
2016-11-08T09:08:53.608873+01:00 INFO bluetoothd[2376]: Player registered: sender=:1.28 path=/org/chromium/Cras/Bluetooth/DefaultPlayer

Comment 1 by fbeaufort@chromium.org, Nov 8 2016

Description: Show this description

Comment 2 by fbeaufort@chromium.org, Nov 8 2016

Description: Show this description

Comment 3 by fbeaufort@chromium.org, Nov 8 2016 

There are 2 errors:


# Failed to open RFKILL control device

According to BlueZ folks, "it is for handling rfkill switches, eg radio off on laptop etc. they expect this is something every linux box should provide".
What I've noticed is that my /dev/rfkill file is owner by root user which explains why it fails as bluetooth user doesn't have access.
If we were to use rfkill, bluetoothd would use it to restore adapter powered state when rfkill is unblocked.


# Failed to obtain handles for "Service Changed" characteristic

A patch is being uploaded at http://marc.info/?l=linux-bluetooth&m=147859465302845&w=2 to address this issue:

Wait until GAP and GATT service are registered to register attribute
handlers otherwise it may attempt to generate service changed without
having service changed registered which leads to print errors:
bluetoothd[2376]: Failed to obtain handles for "Service Changed" characteristic

We'll need to apply it our BlueZ implementation afterwards.

Comment 4 by mcchou@chromium.org, Nov 8 2016

Cc: mcchou@chromium.org

Comment 5 by fbeaufort@chromium.org, Nov 10 2016

Cc: -mcchou@chromium.org
Owner: mcchou@chromium.org
Status: Available (was: Unconfirmed)
mcchou@ Can you apply http://git.kernel.org/cgit/bluetooth/bluez.git/commit/?id=f558fca8d64e3795b0654a90d343af1dd1d8b33c to chromeos-5.41 branch to fix the second error "Failed to obtain handles for "Service Changed" characteristic"?

Comment 6 Deleted

Comment 7 by mcchou@chromium.org, Nov 14 2016 

I also saw the same error messages printed in /var/log/messages when BlueZ starts up. The patch mentioned in comment #5 is picked as https://chromium-review.googlesource.com/#/c/410901. Thanks.

Comment 8 by mcchou@chromium.org, Nov 30 2016

Status: Fixed (was: Available)

Comment 9 by pbath...@chromium.org, Dec 21 2016

Status: Verified (was: Fixed)
verified on 9107.0.0

Comment 10 by kirtika@chromium.org, Mar 21 2017 

Just making a note here that the "Failed to open RFKILL control device" shows up on most Intel 3.18 systems I look at, and it takes some effort to ignore this. 
Is it feasible to have it removed, considering its a given that Chrome OS does not support hardware rfkill?
►

Sign in to add a comment