On 03/11/2014 11:01 PM, Peter Hurley wrote:
On 03/11/2014 10:14 PM, Marcel Holtmann wrote:
Hi Scott,
3.10 with bluetooth-next applied - btmon of both sides attached
I am seeing the same with bluetooth-next on a 3.13 kernel. It even has a weird pattern for me.
rctest[52844]: Connected [handle 11, class 0x000000, priority 0]
rctest[52844]: Can't connect: Device or resource busy (16)
rctest[52844]: Can't connect: Device or resource busy (16)
rctest[52844]: Can't connect: Device or resource busy (16)
rctest[52844]: Can't connect: Device or resource busy (16)
rctest[52844]: Can't connect: Device or resource busy (16)
rctest[52844]: Can't connect: Device or resource busy (16)
rctest[52844]: Can't connect: Device or resource busy (16)
rctest[52844]: Can't connect: Device or resource busy (16)
rctest[52844]: Can't connect: Device or resource busy (16)
rctest[52844]: Can't connect: Device or resource busy (16)
rctest[52844]: Can't connect: Device or resource busy (16)
rctest[52844]: Can't connect: Device or resource busy (16)
rctest[52844]: Can't connect: Connection refused (111)
rctest[52844]: Can't connect: Connection reset by peer (104)
rctest[52844]: Can't connect: Connection reset by peer (104)
rctest[52844]: Connected [handle 11, class 0x000000, priority 0]
Unfortunately I currently have no idea on why this happens. When using
SO_LINGER of 60 seconds with rctest -L 60 -c <bdaddr> I am getting some
really odd tracing behavior.
ACL Data RX: Handle 11 flags 0x02 dlen 14
L2CAP: Command Reject (0x01) ident 7 len 6
Reason: Invalid CID in request (0x0002)
Destination CID: 64
Source CID: 0
This should never happen and makes me wonder if something is
even screwed up one down in L2CAP. Do you happen to have time
to bisect this and figure out which patch introduced this behavior.
Sorry, I was wrong about the UA non-receipt; found it much further
down in the kernel trace. There's quite a lag between sending
the DISC and receiving the UA reply; about 12ms.
--
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
