Re: Touchpad errors

Dmitrij Bogush
2005-08-02T20:14:34Z

Hi.
I have the same issue on Acer Aspire 1520 notebook. On SuSE 9.3 system
can not boot with acpi=off.
In 2.6.13-rc4-git4 this crazy touchpad jumps reports as:

warning: many lost ticks.
Your time source seems to be instable or some driver is hogging interupts
rip handler_IRQ_event+0x20/0x60

and sometimes I can see

psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte N

This happens when some software check battery state or current cpu
rate too often.

2005/8/2, Dmitry Torokhov <dmitry.torokhov@gmail.com>:
> 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
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>