Hi Peter, On Fri, Sep 04, 2009, Peter Hurley wrote: > Maybe. The race I'm observing may have something to do with your > auth_cb fix (tbh, I don't fully understand the sequence avdtp_confirm_cb > -> avdtp_connect_cb -> session_cb and how auth_cb fits in). > > Here's the daemon log (notice the "Transport endpoint is not connected > (107)" errors): > <debug logs snipped> > If this is related to the auth_cb fix, would you please explain how? No, it doesn't look like it's related. The "Transport endpoint is not connected" error is what's returned by the kernel when bluetoothd tries to write to the AVDTP L2CAP socket. What kernel version are you running? I remember us having a similar issue when the DEFER_SETUP socket option was originally introduced. The output of hcidump might also reveal something interesting. 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
