public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Micheal Marineau <marineam@engr.orst.edu>
To: Dmitry Torokhov <dtor_core@ameritech.net>
Cc: linux-kernel@vger.kernel.org, Vojtech Pavlik <vojtech@suse.cz>
Subject: Re: ALPS psmouse_reset on reconnect confusing Tecra M2
Date: Sun, 10 Jul 2005 00:17:16 -0700	[thread overview]
Message-ID: <42D0CB7C.2070005@engr.orst.edu> (raw)
In-Reply-To: <42D0C356.9070102@engr.orst.edu>

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

Micheal Marineau wrote:
> Dmitry Torokhov wrote:
> 
>>On Tuesday 05 July 2005 23:53, Micheal Marineau wrote:
>>
>>
>>>Dmitry Torokhov wrote:
>>>
>>>
>>>>On Monday 04 July 2005 16:14, Mike Waychison wrote:
>>>>
>>>>
>>>>
>>>>>Hi,
>>>>>
>>>>>I just upgrade my Tecra M2 this weekend to the latest GIT tree and
>>>>>noticed that my mouse pointer/touchpad is now broken on resume.
>>>>>
>>>>>Investigating, it appears that mouse device gets confused due to the
>>>>>introduced psmouse_reset(psmouse) during reconnect:
>>>>>
>>>>>http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=f3a5c73d5ecb40909db662c4d2ace497b25c5940
>>>>
>>>>
>>>>Hi,
>>>>
>>>>Please try the following patch:
>>>>
>>>>	http://www.ucw.cz/~vojtech/input/alps-suspend-typo
>>>>
>>>
>>>This fixed the problem for mylaptop, but ONLY if I had #define DEBUG in
>>>alps.c, switch it back to the usual #undef and the exact same problem
>>>happens.  I've got no idea what's going on, I'll poke at it more when
>>>I'm awake....
>>>
>>
>>
>>Hi,
>>
>>Sorry, any update on this topic? Does it still only work with DEBUG?
>>
>>Thanks!
> 
> 
> I have no clue why DEBUG helped, but it seems to have been simply dumb
> luck as the issue came up again with DEBUG still on.  An easy workaround
> was to compile psmouse as a module and unload/load it during the suspend
> cycle (automatic with the hibernate script, it has psmouse in it's
> blacklist).  I haven't dug into it to see what exactly doesn't get
> initilized during resume that should.
> 
> 

Here's a little more info though:
dmesg on boot/re-load module
alps.c: E6 report: 00 00 64
alps.c: E7 report: 63 03 c8
alps.c: E6 report: 00 00 64
alps.c: E7 report: 63 03 c8
alps.c: Status: 10 00 64

dmesg after a resume (no reloading of the module)
alps.c: E6 report: 00 00 64
alps.c: E7 report: 63 03 c8
alps.c: Status: 10 00 64
alps.c: Status: 10 00 64


-- 
Michael Marineau
marineam@engr.orst.edu
Oregon State University


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]

  parent reply	other threads:[~2005-07-10  7:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-04 21:14 ALPS psmouse_reset on reconnect confusing Tecra M2 Mike Waychison
2005-07-04 22:05 ` Dmitry Torokhov
2005-07-05 13:38   ` Mark Lord
2005-07-05 16:40   ` Mike Waychison
2005-07-06  4:53   ` Micheal Marineau
2005-07-10  6:36     ` Dmitry Torokhov
2005-07-10  7:17       ` Micheal Marineau
     [not found]       ` <42D0C356.9070102@engr.orst.edu>
2005-07-10  7:17         ` Micheal Marineau [this message]
2005-07-10  8:03       ` Micheal Marineau
2005-07-10 12:21         ` Vojtech Pavlik
2005-07-10 20:06           ` Micheal Marineau

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=42D0CB7C.2070005@engr.orst.edu \
    --to=marineam@engr.orst.edu \
    --cc=dtor_core@ameritech.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vojtech@suse.cz \
    /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