[Bug 907818] Re: Bluetooth is not fully re-initialized when rfkill switch is toggled

[James M. Leddy]

Initial analysis :

Init:

bluetoothd[1982]: src/main.c:main() Entering main loop
bluetoothd[1982]: src/rfkill.c:rfkill_event() RFKILL event idx 0 type 1 op 0 soft 0 hard 0
bluetoothd[1982]: src/rfkill.c:rfkill_event() RFKILL event idx 1 type 2 op 0 soft 0 hard 0
bluetoothd[1982]: src/rfkill.c:rfkill_event() RFKILL event idx 2 type 2 op 0 soft 0 hard 0
bluetoothd[1982]: src/rfkill.c:rfkill_event() RFKILL event idx 3 type 1 op 0 soft 0 hard 0
bluetoothd[1982]: plugins/hciops.c:init_known_adapters()
bluetoothd[1982]: plugins/hciops.c:init_device() hci0

Flip switch off:

bluetoothd[1982]: src/rfkill.c:rfkill_event() RFKILL event idx 3 type 1 op 2 soft 0 hard 1
bluetoothd[1982]: HCI dev 0 down

Flip switch on:

bluetoothd[1982]: src/rfkill.c:rfkill_event() RFKILL event idx 2 type 2 op 1 soft 0 hard 0
bluetoothd[1982]: src/rfkill.c:rfkill_event() RFKILL event idx 0 type 1 op 2 soft 1 hard 1
bluetoothd[1982]: src/rfkill.c:rfkill_event() RFKILL event idx 1 type 2 op 2 soft 1 hard 1
bluetoothd[1982]: src/rfkill.c:rfkill_event() RFKILL event idx 3 type 1 op 2 soft 0 hard 0
bluetoothd[1982]: HCI dev 0 registered
bluetoothd[1982]: plugins/hciops.c:init_device() hci0
bluetoothd[1982]: Listening for HCI events on hci0
bluetoothd[1982]: plugins/hciops.c:init_device() child 1998 forked
bluetoothd[1982]: src/rfkill.c:rfkill_event() RFKILL event idx 4 type 2 op 0 soft 0 hard 0
bluetoothd[1982]: src/rfkill.c:rfkill_event() RFKILL event idx 4 type 2 op 2 soft 0 hard 0
bluetoothd[1982]: plugins/hciops.c:read_local_features_complete() Got features for hci0
bluetoothd[1982]: plugins/hciops.c:read_local_version_complete() Got version for hci0
bluetoothd[1982]: plugins/hciops.c:read_bd_addr_complete() hci0 status 0
bluetoothd[1982]: plugins/hciops.c:read_bd_addr_complete() Got bdaddr for hci0
bluetoothd[1982]: plugins/hciops.c:read_local_name_complete() hci0 status 0
bluetoothd[1982]: plugins/hciops.c:read_local_name_complete() Got name for hci0
bluetoothd[1982]: plugins/hciops.c:read_tx_power_complete() hci0 status 0
bluetoothd[1982]: plugins/hciops.c:update_ext_inquiry_response() hci0
bluetoothd[1982]: HCI dev 0 up

Some other event I don't know what is, may be cleanup:

bluetoothd[1982]: src/rfkill.c:rfkill_event() RFKILL event idx 0 type 1 op 2 soft 0 hard 0
bluetoothd[1982]: src/rfkill.c:rfkill_event() RFKILL event idx 1 type 2 op 2 soft 0 hard 0
bluetoothd[1982]: src/adapter.c:adapter_remove() Removing adapter /org/bluez/1982/hci0
bluetoothd[1982]: src/sdpd-service.c:remove_record_from_server() Removing record with handle 0x10005

What I find interesting is that idx 0,1 are not re-enabled when the
switch is flicked back on, only some time later, if I'm reading the
output of rfkill_event() correctly.

** Tags added: blocks-hwcert-enablement

** Tags removed: blocks-hwcert-enablement
** Tags added: rls-p-tracking

** Tags added: blocks-hwcert-enablement

-- 
You received this bug notification because you are a member of
Bluetooth, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/907818

Title:
  Bluetooth is not fully re-initialized when rfkill switch is toggled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/907818/+subscriptions