From: Chase Douglas <chase.douglas@canonical.com>
To: Ed Tomlinson <edt@aei.ca>
Cc: linux-kernel@vger.kernel.org, rydberg@euromail.se,
jkosina@suse.cz, linux-input@vger.kernel.org
Subject: Re: [regression] Apple Magic Mouse stalls
Date: Fri, 03 Jun 2011 15:48:07 -0400 [thread overview]
Message-ID: <4DE93A77.1070404@canonical.com> (raw)
In-Reply-To: <201105281006.33763.edt@aei.ca>
On 05/28/2011 10:06 AM, Ed Tomlinson wrote:
> Hi
>
> I've been having fun with bluetooth in .38-rc. My adapter was old (bt 1.1) and the bluetooth stack was having 'fun' with it.
> Got tired of that a got asus doggle that supports 2.1+EDR. Then I tried to use my magic mouse. It works for a few
> minutes and then stalls. The stalls seem to be related to touches. If I am careful only to touch with one finger it
> seems to work. It usually works with two fingers, with three it stalls. Running hcidump sometimes lists a last
> packet with a dlen of 35 when it stalls. Powering it on an off reset things
>
>> ACL data: handle 21 flags 0x02 dlen 27
> L2CAP(d): cid 0x0041 len 23 [psm 0]
>> ACL data: handle 21 flags 0x02 dlen 27
> L2CAP(d): cid 0x0041 len 23 [psm 0]
>> ACL data: handle 21 flags 0x02 dlen 27
> L2CAP(d): cid 0x0041 len 23 [psm 0]
>> ACL data: handle 21 flags 0x02 dlen 35
> L2CAP(d): cid 0x0041 len 31 [psm 0]
>
> This was not a problem pre .38. It started happening in .38-rc along with other bluetooth problems. I figured the bt
> problem was the root cause - I was wrong.
>
> This ring any bells?
Not for me... Nothing has changed in the driver that could cause such a
change, so if there is a regression it exists somewhere else in the stack.
Jiri, any thoughts?
-- Chase
prev parent reply other threads:[~2011-06-03 19:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-28 14:06 [regression] Apple Magic Mouse stalls Ed Tomlinson
2011-06-03 19:48 ` Chase Douglas [this message]
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=4DE93A77.1070404@canonical.com \
--to=chase.douglas@canonical.com \
--cc=edt@aei.ca \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rydberg@euromail.se \
/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.