Export to GitHub

btstack - issue #416

hci_number_free_acl_slots: handle 0x0000 not in connection list


Posted on Aug 25, 2014 by Happy Monkey

Hi!

The code seems to work normally currently. I have classic Bluetooth and a BLE peripheral working at the moment using BTstack.

I have enabled info and error logging. However, I always receive the above error message.

I guess that this might be a result of specifiying the connection parameter in some function calls as NULL.

What would be the correct way of resolving this so that the error message does not appear anymore?

Comment #1

Posted on Aug 25, 2014 by Swift Ox

the guess about not specifying the handle properly is correct. I've already fixed it in the l2cap_run method. Do you know from where you get the calls with handle 0x0000.

Comment #2

Posted on Aug 27, 2014 by Swift Ox

One other place is sm_run().. I'll go over that tomorrow

Comment #3

Posted on Aug 27, 2014 by Happy Monkey

Correct. In my code it is also always sm_run(). It is caused by the check l2cap_can_send_fixed_channel_packet_now(). Callstack: hci_number_free_acl_slots_for_handle() hci_can_send_prepared_acl_packet_now() hci_can_send_acl_packet_now() l2cap_can_send_fixed_channel_packet_now() sm_run()

Comment #4

Posted on Aug 28, 2014 by Swift Ox

Fixed in sm.c and in hci.c to first post disconnect event and then shutdown the connection. Do you get more of these after updating to the current version?

Comment #5

Posted on Aug 28, 2014 by Happy Monkey

The messages are gone now. Thanks!

Comment #6

Posted on Aug 28, 2014 by Swift Ox

(No comment was entered for this change.)

Status: Fixed

Labels:
Type-Defect Priority-Medium