From: Pete Zaitcev <zaitcev@redhat.com>
To: Peter Osterlund <petero2@telia.com>
Cc: vojtech@suse.cz, linux-kernel@vger.kernel.org, zaitcev@redhat.com
Subject: Re: Touchpad problems with 2.6.11-rc2
Date: Mon, 31 Jan 2005 15:15:49 -0800 [thread overview]
Message-ID: <20050131151549.26f437b0@localhost.localdomain> (raw)
In-Reply-To: <m3acqr895h.fsf@telia.com>
Hello, Peter:
The keyboard seems to work now, but I stepped on a very strange condition.
Suddenly, touchpad motions started to cause wild movements in it became
impossible to do anything due to a focus loss (of course, I had plenty of
modified files open :-)
The dmesg looked like this:
psmouse.c: TouchPad at isa0060/serio1/input0 lost sync at byte 3
psmouse.c: TouchPad at isa0060/serio1/input0 - driver resynched.
psmouse.c: TouchPad at isa0060/serio1/input0 lost sync at byte 3
psmouse.c: TouchPad at isa0060/serio1/input0 lost sync at byte 1
psmouse.c: TouchPad at isa0060/serio1/input0 lost sync at byte 1
psmouse.c: TouchPad at isa0060/serio1/input0 - driver resynched.
psmouse.c: TouchPad at isa0060/serio1/input0 lost sync at byte 1
psmouse.c: TouchPad at isa0060/serio1/input0 lost sync at byte 1
psmouse.c: TouchPad at isa0060/serio1/input0 lost sync at byte 1
psmouse.c: TouchPad at isa0060/serio1/input0 lost sync at byte 1
psmouse.c: TouchPad at isa0060/serio1/input0 lost sync at byte 3
psmouse.c: TouchPad at isa0060/serio1/input0 - driver resynched.
psmouse.c: TouchPad at isa0060/serio1/input0 lost sync at byte 3
psmouse.c: TouchPad at isa0060/serio1/input0 - driver resynched.
psmouse.c: TouchPad at isa0060/serio1/input0 lost sync at byte 3
psmouse.c: TouchPad at isa0060/serio1/input0 - driver resynched.
Now I'm afraid to run that kernel again (2.6.11-rc2 + your patches
1/4 and 2/4).
I run that kernel with hardware tap disabled (tap_time = 0).
-- Pete
next prev parent reply other threads:[~2005-01-31 23:16 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-24 3:01 Touchpad problems with 2.6.11-rc2 Pete Zaitcev
2005-01-30 11:10 ` Peter Osterlund
2005-01-31 23:15 ` Pete Zaitcev [this message]
2005-02-01 3:40 ` Dmitry Torokhov
2005-02-01 5:06 ` Pete Zaitcev
2005-02-01 5:14 ` Dmitry Torokhov
2005-02-03 11:18 ` Giuseppe Bilotta
2005-02-02 7:41 ` Pete Zaitcev
2005-02-02 10:20 ` Vojtech Pavlik
2005-02-02 15:51 ` Dmitry Torokhov
2005-02-02 15:57 ` Vojtech Pavlik
2005-02-02 16:56 ` Pete Zaitcev
2005-02-02 17:07 ` Vojtech Pavlik
2005-02-02 17:58 ` Pete Zaitcev
2005-02-02 19:11 ` Vojtech Pavlik
2005-02-02 19:39 ` Pete Zaitcev
2005-02-02 19:55 ` Vojtech Pavlik
2005-02-02 19:39 ` Dmitry Torokhov
2005-02-03 8:30 ` Alexandre Oliva
2005-02-03 8:49 ` Vojtech Pavlik
2005-02-03 15:17 ` Alexandre Oliva
2005-02-03 15:28 ` Dmitry Torokhov
2005-02-03 15:45 ` Vojtech Pavlik
2005-02-02 20:57 ` Peter Osterlund
2005-02-02 21:17 ` Dmitry Torokhov
2005-02-02 21:47 ` Peter Osterlund
2005-02-02 22:06 ` Dmitry Torokhov
2005-02-02 22:27 ` Peter Osterlund
2005-02-03 7:16 ` Dmitry Torokhov
2005-02-02 21:37 ` David Ford
2005-02-02 22:11 ` Pete Zaitcev
2005-02-02 22:58 ` Peter Osterlund
2005-02-03 6:46 ` Vojtech Pavlik
2005-02-03 21:54 ` Peter Osterlund
2005-02-04 6:17 ` Vojtech Pavlik
2005-02-04 6:40 ` Peter Osterlund
2005-02-04 6:53 ` Vojtech Pavlik
2005-02-04 7:33 ` Peter Osterlund
2005-02-04 13:25 ` Vojtech Pavlik
2005-02-04 13:23 ` Vojtech Pavlik
2005-02-03 6:59 ` Pete Zaitcev
-- strict thread matches above, loose matches on Subject: below --
2005-01-25 19:55 David Brownell
2005-01-25 21:30 ` Dmitry Torokhov
2005-01-30 11:20 ` Peter Osterlund
2005-01-30 20:59 ` David Brownell
2005-01-31 21:46 ` Pete Zaitcev
2005-01-31 22:00 ` Dmitry Torokhov
2005-02-08 10:55 Stephane Raimbault
2005-02-08 17:05 ` Peter Osterlund
2005-02-09 8:47 ` Stephane Raimbault
2005-02-09 18:09 ` Peter Osterlund
2005-02-10 8:32 ` Stephane Raimbault
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=20050131151549.26f437b0@localhost.localdomain \
--to=zaitcev@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=petero2@telia.com \
--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 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.