Re: Feature Request: Clean the cache upon device disconnection

Hi François,

On Thu, Mar 10, 2016 at 1:41 PM, François Beaufort
[off-list ref] wrote:

Are there more logs I can provide to help diagnose this issue?

D-Bus perhaps would help, but you will probably have to enable
eavesdrop so you can actually see the responses:

https://wiki.ubuntu.com/DebuggingDBus

On Thu, Mar 10, 2016 at 12:26 PM, Luiz Augusto von Dentz
[off-list ref] wrote:

quoted

Hi François,

On Thu, Mar 10, 2016 at 1:01 PM, François Beaufort
[off-list ref] wrote:

quoted

On Thu, Mar 10, 2016 at 11:54 AM, Luiz Augusto von Dentz
[off-list ref] wrote:

quoted

Hi François,

On Thu, Mar 10, 2016 at 12:15 PM, François Beaufort
[off-list ref] wrote:

quoted

Here are failing bluetoothd and hcidump logs with BlueZ at commit
c8a81f43921cf417e270f3b6e0b0118cbc27a58d

git log c8a81f43921cf417e270f3b6e0b0118cbc27a58d
fatal: bad object c8a81f43921cf417e270f3b6e0b0118cbc27a58d

Seems like it is not a valid object, is this based on upstream?

It is: http://git.kernel.org/cgit/bluetooth/bluez.git/commit/?id=c8a81f43921cf417e270f3b6e0b0118cbc27a58d

Sorry forgot to update since yesterday.

quoted

quoted

quoted

http://pastebin.com/raw/i416k6aw

I can see the old services being removed and the new one being added:

old services:
bluetoothd[8323]: src/gatt-client.c:unregister_service() Removing GATT
service: /org/bluez/hci0/dev_F1_6F_DE_EC_F1_D6/service0012
bluetoothd[8323]: src/gatt-client.c:unregister_service() Removing GATT
service: /org/bluez/hci0/dev_F1_6F_DE_EC_F1_D6/service0016
bluetoothd[8323]: src/gatt-client.c:unregister_service() Removing GATT
service: /org/bluez/hci0/dev_F1_6F_DE_EC_F1_D6/service0019

new service:

bluetoothd[8323]: src/gatt-client.c:service_create() Exported GATT
service: /org/bluez/hci0/dev_F1_6F_DE_EC_F1_D6/service000c
bluetoothd[8323]: src/gatt-client.c:characteristic_create() Exported
GATT characteristic:
/org/bluez/hci0/dev_F1_6F_DE_EC_F1_D6/service000c/char000d
bluetoothd[8323]: src/gatt-client.c:characteristic_create() Exported
GATT characteristic:
/org/bluez/hci0/dev_F1_6F_DE_EC_F1_D6/service000c/char000f
bluetoothd[8323]: src/gatt-client.c:descriptor_create() Exported GATT
characteristic descriptor:
/org/bluez/hci0/dev_F1_6F_DE_EC_F1_D6/service000c/char000f/desc0011
bluetoothd[8323]: src/gatt-client.c:characteristic_create() Exported
GATT characteristic:
/org/bluez/hci0/dev_F1_6F_DE_EC_F1_D6/service000c/char0012

quoted

http://pastebin.com/raw/5dC9dFiP

So it fails here:

2016-03-10 11:11:49.083776 < ACL data: handle 32 flags 0x00 dlen 9
    ATT: Write req (0x12)
      handle 0x000b value  0x02 0x00
2016-03-10 11:11:49.118038 > ACL data: handle 32 flags 0x02 dlen 5
    ATT: Write resp (0x13)

It is trying to write to handle 0x000b which is not in the range of
the new services, in fact is probably the service changed
characteristic CCC:

bluetoothd[8323]: src/device.c:gatt_debug() start: 0x0008, end:
0x000b, uuid: 00001801-0000-1000-8000-00805f9b34fb

That is GATT service:

#define GATT_UUID "00001801-0000-1000-8000-00805f9b34fb"

So there is nothing in the logs related to the application, it is
perhaps something in the above layers, perhaps it could not be
detecting the service removal properly. I did a quick test here with
zephyr as peripheral and changing services do actually appear in
bluetoothctl.

Do you have a nRF51 Dev Kit you could use to replicate locally this issue?

No, but there is nothing we couldn't do with zephyr or BlueZ I
suppose. But as I mentioned above it doesn't look like is something
that even reached HCI so I suppose there is something else wrong,
perhaps you are trying to access objects that don't exist anymore.

--
Luiz Augusto von Dentz

-- 
Luiz Augusto von Dentz