From: Steven Davies <linux-bluetooth-list@steev.me.uk>
To: linux-bluetooth <linux-bluetooth@vger.kernel.org>
Subject: Re: After bluetoothd disconnects a LE device only restart of kernel modules allows it to reconnect
Date: Tue, 27 Oct 2015 10:22:27 +0000 [thread overview]
Message-ID: <562F5063.2020809@steev.me.uk> (raw)
In-Reply-To: <1E7A740C-DA0A-45F0-8F03-BA21BC5F37B2@holtmann.org>
Hi Marcel,
> Hi Steven,
>
>> I'm using bluez-5.35 with kernel 4.2 and am seeing that after a while (could be minutes, hours or days, I don't know what the trigger is) a BLE device will disconnect and the only way to reconnect to it is to rmmod the bluetooth modules and re-modprobe them. Obviously this shouldn't happen. I'm seeing the following output from bluetoothd (sorry for the huge log, let me know if a full pastebin would be better). Can anyone offer any insight into why once this happens, I can't talk to the device through Bluetooth?
> can you also show the btmon for this situation. And any chance to test 4.2.x stable kernel. A few patches went into stable kernel that might fix this. I would be also great if you can do a quick test with 4.3-rc7 and bluetooth-next kernels to see if this might be something that we already fixed.
The best I can do at the moment is 4.3-rc6 since this is running on an
ARM dev board that needs a special set of kernel patches. I've started
my program running on that and am running btmon as well. If the issue
happens again I'll post back with the btmon log.
--
Regards
Steven Davies
next prev parent reply other threads:[~2015-10-27 10:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-24 17:12 After bluetoothd disconnects a LE device only restart of kernel modules allows it to reconnect Steven Davies
2015-10-25 20:09 ` Marcel Holtmann
2015-10-27 10:22 ` Steven Davies [this message]
2015-11-02 10:22 ` Steven Davies
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=562F5063.2020809@steev.me.uk \
--to=linux-bluetooth-list@steev.me.uk \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.