From: bryan@varnernet.com
To: linux-bluetooth@vger.kernel.org
Subject: BT Mouse intermittent disconnects
Date: Tue, 20 Jun 2017 17:31:45 -0400 [thread overview]
Message-ID: <1497994305.1739.6.camel@localhost> (raw)
Greetz.
To start: Just picked up a new laptop with built in BT. woo!
Paired a mouse I've been using with OS X for years. On OS X if it was
idle for a while, it would take a _long_ time to reconnect, and I'd see
the blue 'pairing' light flash a few times.
So with the new laptop on Linux 4.11.6 (and 4.9.30 -- from debian 9)
i'm seeing the following end-user behavior:
While using the mouse to interact with the system, it will just
disconnect and repair. I can be in the middle of a window drag, and it
drops.
I've spent the last day or so doing all the input driver debugging to
rule out:
* HID driver issues
* USB Power Management
I've tried using HIDP in the kernel, UHID out of kernel.
What I saw from uhid was that the read() call would return '0',
resulting in a 'disconnect reason 2'. In kernel mode, it's a bit less
verbose about things.
Since I'd rather not dump btmon dumps into the mailing list, here's a
link to the raw output of a mon session when the issue occurs.
https://pastebin.com/raw/x7nMmL0p
I'm pretty much a newb when it comes to BT stuff, but from the looks of
it, things seem to regularly go wonky when there's a sniff mode
transition.
I also have a BT keyboard that likkkkkkes to occccasssssssssssionally
expresssss a desire to stiiiiiiick. I didn't have the keyboard paired
(or powered on) during the above session. I've been unable to find a
reason for the keyboard to be acting funny.
What can I do to improve the situation for myself and others?
Can you folks point me in the right direction to try to troubleshoot /
understand / fix this?
Regards,
-Bryan
reply other threads:[~2017-06-20 21:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1497994305.1739.6.camel@localhost \
--to=bryan@varnernet.com \
--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.