Hi, First of all, please don't top-post on this list. On Mon, Jul 02, 2012, bubba junk wrote: > I was wondering if you've had a chance to review the output of the > hcidump and list-devices that you requested me to provide. I noticed > the text "Connection refused - security block" in the output. Prior to > the following patch, I was not able to connect my headset using the > panel applet: [PATCH] Bluetooth: Fix l2cap connfailures for ssp > devices. Since that patch, I am now able to connect the headset using > the panel applet, but the headset does not connect automatically. > Based on the output, is this another bug related to SSP? I'll copy-paste it below: > >> ACL data: handle 11 flags 0x02 dlen 12 > > L2CAP(s): Connect req: psm 3 scid 0x0041 > > < ACL data: handle 11 flags 0x00 dlen 16 > > L2CAP(s): Connect rsp: dcid 0x0000 scid 0x0041 result 3 status 0 > > Connection refused - security block > >> HCI Event: Encrypt Change (0x08) plen 4 > > status 0x00 handle 11 encrypt 0x01 This looks like a well known hardware bug where the controller doesn't send HCI events and ACL data packets in the right order. If you had an air sniffer you'd probably see that the link is encrypted *before* the L2CAP Connect request is sent (as opposed to after it as the log above indicates). For connect requests to non-SDP PSMs coming before an encrypted link a security block response is the correct behavior for BlueZ. Johan -- 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
