Hi, On Tue, Oct 20, 2009 at 10:38 AM, Johan Hedberg <johan.hedberg@xxxxxxxxx> wrote: > Hi, > > On Fri, Oct 16, 2009, Valmantas Palikša wrote: >> Steps to reproduce: >> 1. rfkill block bluetooth >> 2. start bluetoothd >> 3. kill bluetoothd > > I don't seem to have rfkill support (at least using that command) on my > laptop so I can't verify this fix, but could you try the attached patch > and see if it resolves the issue? The problem seems to be that in this use > case we never load/probe the adapter drivers but still call their remove > callbacks when the adapter initialization fails. This causes some drivers > to call btd_adapter_unref on adapter objects for which they do not own a > reference. Yep, it fixes the problem. -- Luiz Augusto von Dentz Engenheiro de Computação -- 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
