public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Brian Rogers <brian@xyzw.org>
To: linux-bluetooth@vger.kernel.org
Subject: Mouse connection times out in sniff mode
Date: Mon, 18 May 2009 00:26:50 -0700	[thread overview]
Message-ID: <4A110DBA.1060704@xyzw.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1541 bytes --]

Hi all,

I have a problem where my mouse occasionally disconnects after brief 
inactivity.

Using hcidump, I can see it dropping to sniff mode during the 
inactivity. Then, if the problem occurs, no activity is logged when I 
move or click the mouse until it gets disconnected due to a timeout. 
Once the timeout occurs, the mouse is able to reconnect.

Other times the mouse comes out of sniff mode just fine. The frequency 
of this problem occurring seems rather random. Sometimes I can't 
reproduce it, and other times it happens constantly. I've also done a 
bit of testing with two other Bluetooth dongles, and the problem seems 
to occur only with my laptop's internal Bluetooth device.

I've been able to work around the timeout problem by disabling sniff 
mode. I've been using the following command:
sudo hciconfig hci0 lp hold,park lm master

Also, this problem is exposing a secondary issue. When the connection 
times out in the scenario described above, the mouse is not removed from 
HAL. So I see many many copies of the mouse piling up in 
gnome-device-manager and 'xinput list'. If I switch the mouse off 
myself, the mouse (or at least the most recent copy) is properly removed 
once the timeout occurs. I think being in sniff mode when the timeout 
happens is what makes the difference.

My configuration:

Bus 002 Device 002: ID 0a5c:2101 Broadcom Corp. A-Link BlueUsbA2 Bluetooth
Linux master branch with bluetooth-testing branch merged in.
BlueZ 4.39

A log of the timeout happening a couple times is attached.

Brian


[-- Attachment #2: hcidump.log.bz2 --]
[-- Type: application/x-bzip, Size: 4925 bytes --]

                 reply	other threads:[~2009-05-18  7:26 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=4A110DBA.1060704@xyzw.org \
    --to=brian@xyzw.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox