Hi Manuel, On Fri, Sep 3, 2010 at 4:28 AM, Manuel Naranjo <manuel@xxxxxxxxxxxx> wrote: > Luiz, >> >> In situation where the user application keep a discovery session while >> bonding with a device it may cause a delay, or even timeout, due to the >> number of the inquiry responses that the controller has to process. >> >> Since the discovery can be shared between many applications it may not be >> possible to simple require to each application to stop their discovery >> before trying to pair with a device, so to fix this bluetoothd now >> suspends the discovery while bonding, resuming when completed. > > Stupid question but... Any way this is related to my seg faults during sdp > resolving problems? I haven't tried to fix it in a while, so far I'm ok with > a stupid cron rule which revives bluetoothd if it crashes, but I would > prefer a better solution. I don't think it fixes your problem, but you better check if bluetoothd is still crashing as before, apparently nobody else is having the same problem so it is quite tricky to resolve it. Regards, -- 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
