michelcandido / btstack

Automatically exported from code.google.com/p/btstack
0 stars 0 forks source link

l2cap: hci_number_completed_packet but no outgoing packet in records #150

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
When BTstack is SDP browsed by a remote machine, it provides a SDP record. In 
the process it reports
--
hci_number_completed_packet but no outgoing packet in records
--

The error means that the flow control system saw a 'ack' when it didn't know a 
packet had been sent out.

It looks like this happens with:
1). Packets without a recognised handle (ie, handle is not in
'l2cap_channels' linked list) - adding handle check fixes that.
2). 'Signaling packets' - I guess the solution is to detect whether
link is established (ie. handle _is_  in 'l2cap_channels' linked lis)
and then start counting these packets as well. This seems to be done
for normal packets, so code could be duplicated/re-used. 

Simon

Original issue reported on code.google.com by mungew...@gmail.com on 3 May 2011 at 3:26

GoogleCodeExporter commented 8 years ago
Have a solution, will post patch later...

Original comment by mungew...@gmail.com on 3 May 2011 at 5:11

GoogleCodeExporter commented 8 years ago
very good :)

Original comment by matthias.ringwald@gmail.com on 3 May 2011 at 5:36

GoogleCodeExporter commented 8 years ago
yes was working on this last night when SO told me that it was time too stop.

Patch attached.
Simon

Original comment by mungew...@gmail.com on 4 May 2011 at 4:04

Attachments:

GoogleCodeExporter commented 8 years ago
ups. forgot about that one, but I've basically rewritten the whole flowcontrol. 
should be fine now. :)

Original comment by matthias.ringwald@gmail.com on 25 Jul 2011 at 9:30