Hi Alex, On Wed, Jul 13, 2016 at 1:56 PM, Alexander Aring <aar@xxxxxxxxxxxxxx> wrote: Just use a pastbin url to past the logs, that is probably not many people interested in that. >>> --- >>> >>> They simple show the same stuff, but with different addresses. >>> >>> I rethink about your words and I suppose you told me that tx_credits and >>> -EAGAIN are normal that this stuff occurs. >>> >>> I agree, It also occurs before when I run: >>> >>> ping6 $IP_NODEB%6lo0 -s 60000 >>> >>> which is normal. But what should not happen is that there is some little >>> tiny window (race) that both tx_credits are reached to zero and then >>> nobody transmit anything anymore, that's the tx deadlock which I hit here. >>> >>> And this deadlock occurs that I killed the L2CAP chan connection. I >>> think it will work when I create a new chan (because new tx_credits). >>> The connection isn't broken, I just can not transmit anything because tx_credits. >> >> If there is no calls to channel resume then yes there is a problem >> that no tx_credits would be able to be sent, note though that the >> command the restore credits does happen in the signalling channel not >> in the data channel so there should be anything blocking from > > So these are complete separate transmission? Could it be that, because I > do much things on the air that such "tx_credits command" stuff could not > be reached to the other side? Then the complete mechanism can not be > working and maybe need some recovery if no "tx_credits command reached" > some time ago to solve this deadlock? Well the only information about the credits I have is the rx, which is in fact not 0 as assumed before: rx_credits 8 -> 7 So we didn't even have to restore anything so most likely it is just the tx_credits that goes to 0 which means there is probably a problem with the other box. > I am not a bluetooth expert, maybe there exists nicer solutions. :-) > >> receiving those, perhaps looking into what is happening the last time >> it receives credits and the sequence of calls it generate. >> > > See above, I hope that helps. How about l2cap_le_credits, or is that not called even once? Btw, use btmon -w <file> and just attach the file next time. -- Luiz Augusto von Dentz -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
