Hi, On Sat, Oct 2, 2010 at 4:58 PM, Pacho Ramos <pacho@xxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote: > El lun, 20-09-2010 a las 21:49 +0300, Johan Hedberg escribió: >> Hi, >> >> On Mon, Sep 20, 2010, Pacho Ramos wrote: >> > Reporter found that the problem with his dongle was introduced in commit >> > aee26b30bbc24cde464ba1a557c2b258ddec6432 "Make BtIO default security >> > level MEDIUM", he asked here, on upstream mailing list, but didn't get >> > any reply clarifying this: >> > http://marc.info/?l=linux-bluetooth&m=127893935109510&w=2 >> >> The important piece of info missing here is an HCI trace of the failure >> (i.e. output of hcidump). There was a similar issue reported on IRC a >> few days back and the hcidump there revealed a LMP response timeout >> after BlueZ issues a HCI_Set_Connection_Encryption command. This would >> seem to indicate a bug either in the local adapter or the remote device >> (headset). Only an airtrace would really reveal what's going on. >> However, I suspect it might be possible to work around this by looking >> into possibilities of changing the ordering and timing of when the >> kernel sends the encryption request. >> >> Johan >> > > Sorry for the delay but downstream reporter wasn't able to provide the > information sooner. > > Attached is hcidump output, I hope it helps :-) I would say this was because of double authentication request, but it seems it is not the case, actually ssp doesn't seems to be used at all here so this must be something else, maybe you should try this: http://thread.gmane.org/gmane.linux.bluez.kernel/7256 -- Luiz Augusto von Dentz Computer Engineer -- 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
