From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] MX900 sometimes catalepsic
Date: Wed, 26 Jan 2005 18:42:20 +0100 [thread overview]
Message-ID: <1106761340.28444.46.camel@pegasus> (raw)
In-Reply-To: <1106681895.20288.0.camel@bluez.bueche.ch>
Hi Charles,
> I'm running 2.6.10-gentoo-r4 with patch-2.6.10-mh1.gz. My hardware is a
> Logitech MX900 mouse and a Dell Inspiron 8600 with a CSR chip :
>
> hci0: Type: USB
> BD Address: 00:10:C6:22:54:AF ACL MTU: 192:8 SCO MTU: 64:8
> UP RUNNING PSCAN ISCAN
> RX bytes:113629 acl:7992 sco:0 events:88 errors:0
> TX bytes:1043 acl:24 sco:0 commands:42 errors:0
> Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
> Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
> Link policy: RSWITCH HOLD SNIFF PARK
> Link mode: SLAVE ACCEPT
> Name: 'laptopcb (0)'
> Class: 0x100100
> Service Classes: Object Transfer
> Device Class: Computer, Uncategorized
> HCI Ver: 1.1 (0x1) HCI Rev: 0x235 LMP Ver: 1.1 (0x1) LMP Subver: 0x235
> Manufacturer: Cambridge Silicon Radio (10)
>
> I'm not using the mouse bluetooth dock for any connection (only battery
> loading).
>
> Often, after unpacking my laptop and MX900 mouse from its bag, the mouse
> appear to "hang". The laptop doesn't see it, and I have to open the
> mouse battery location and quickly unplug one battery to reset the
> mouse. After this treatment, the mouse announce itself and the laptop
> sees it and create the devices with udev.
>
> The problem happen about 1/4 of the time when unpacking the laptop, but
> in a systematic way after a reboot (eg after upgrading my kernel). I
> never boot my laptop under Windows, and I never use the mouse with other
> machines. The "connect" button has no effect.
>
> The problem has be present since a long time and several kernels and
> bluez patches, maybe since always.
>
> It would only be annoying, but the battery door of my mouse is starting
> to present a bad shape after openning it with just about all the tools
> that fits it, including cisors.
I have no idea what the problem is, but I assume that it is because of
the reconnect feature of the mouse. I will always try to reconnect when
you move your bag and after some failed retries it may deadlock itself.
On the other hand there is maybe a small race when you shutdown the
machine and disconnect every device. May a "hciconfig hci0 noscan"
before calling "hidd -K" will help.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2005-01-26 17:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-25 19:38 [Bluez-users] MX900 sometimes catalepsic Charles Bueche
2005-01-26 17:42 ` Marcel Holtmann [this message]
2005-02-07 10:21 ` Charles Bueche
2005-02-07 10:36 ` Marcel Holtmann
[not found] <1106636710.13319.6.camel@bluez.bueche.ch>
2005-01-27 0:42 ` Douglas Russell
2005-01-27 5:59 ` Marcel Holtmann
2005-01-27 18:10 ` Bryan Forbes
2005-01-28 16:30 ` puggy
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=1106761340.28444.46.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
/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