From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: sboyce@blueyonder.co.uk
Cc: linux-kernel@vger.kernel.org
Subject: Re: Touchpad errors
Date: Tue, 2 Aug 2005 09:22:12 -0500 [thread overview]
Message-ID: <d120d500050802072256a4d7ee@mail.gmail.com> (raw)
In-Reply-To: <42EF633B.6080209@blueyonder.co.uk>
On 8/2/05, Sid Boyce <sboyce@blueyonder.co.uk> wrote:
> New SuSE 9.3 x86_64 install after HD crash. With 2.6.13-rc3 and up to
> 2.6.13-rc4-git4. I can't remember seeing these errors for quite a long
> time, thought they were fixed, perhaps there is a regression in recent
> kernels.
> It completely and rapidly fills up dmesg and /var/log/messages so I
> can't get other stuff I need to see.
> psmouse.c: TouchPad at isa0060/serio4/input0 - driver resynched.
> psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 4
> psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 4
> psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1
> psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1
> psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 4
> psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1
> psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1
> psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 4
> psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1
> psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1
> psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 4
>
Does it work with acpi=off?
--
Dmitry
next prev parent reply other threads:[~2005-08-02 14:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-02 12:12 Touchpad errors Sid Boyce
2005-08-02 14:22 ` Dmitry Torokhov [this message]
2005-08-02 20:14 ` Dmitrij Bogush
2005-08-02 20:20 ` Lee Revell
2005-08-02 22:46 ` Sid Boyce
2005-08-02 20:29 ` Dmitry Torokhov
2005-08-02 21:58 ` Dmitrij Bogush
2005-08-02 22:06 ` Sid Boyce
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=d120d500050802072256a4d7ee@mail.gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sboyce@blueyonder.co.uk \
/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.