linux-kernel - Re: [regression] Apple Magic Mouse stalls

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <4DE93A77.1070404@canonical.com>
Date:	Fri, 03 Jun 2011 15:48:07 -0400
From:	Chase Douglas <chase.douglas@...onical.com>
To:	Ed Tomlinson <edt@....ca>
CC:	linux-kernel@...r.kernel.org, rydberg@...omail.se, jkosina@...e.cz,
	linux-input@...r.kernel.org
Subject: Re: [regression] Apple Magic Mouse stalls

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/