Touchpad errors

Touchpad errors

[Sid Boyce]

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

Regards
Sid.
-- 
Sid Boyce ... Hamradio License G3VBV, Keen licensed Private Pilot
Retired IBM Mainframes and Sun Servers Tech Support Specialist
Microsoft Windows Free Zone - Linux used for all Computing Tasks

Re: Touchpad errors

[Dmitry Torokhov]

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

Re: Touchpad errors

[Dmitrij Bogush]

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/
>

Re: Touchpad errors

[Lee Revell]

On Wed, 2005-08-03 at 00:14 +0400, Dmitrij Bogush wrote:
> This happens when some software check battery state or current cpu
> rate too often.

Acer laptops are notorious for buggy SMM implementations that disable
interrupts for many timer ticks.  Does it work any better with HZ=100?

Lee

Re: Touchpad errors

[Dmitry Torokhov]

On 8/2/05, Dmitrij Bogush <dmitrij.bogush@gmail.com> wrote:
> 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.
> 

Yes, that would do it. psmouse module drops received byte if it is
delayed for more than 0.5 sec. On some machines getting batetry info
takes a long time and all the time is spent in BIOS with interrupts
disabled. That is why the data is split between state and info - one
is static and takes much longer to access and other is more "dynamic"
and is cheaper to access. Unfortunately some usespace tools check both
and do that like every second.

You may try to talk to ACPI people; also I recommend setting battery
polling interval to something sane, like 1 minute, and make sure your
tool does not touch  "info" file - that should help a bit.

-- 
Dmitry

Re: Touchpad errors

[Dmitrij Bogush]

>Acer laptops are notorious for buggy SMM implementations that disable
>interrupts for many timer ticks.  Does it work any better with HZ=100?

Maybe, but I do not see any difference between 100 and 1000 hz on 2.6.13-rc5. 
With 2.6.13(from rc4) I do not get "crazy jumps" like in 2.6.12 or
later, only freezes for 1 second.

> You may try to talk to ACPI people; also I recommend setting battery
> polling interval to something sane, like 1 minute, and make sure your
> tool does not touch  "info" file - that should help a bit.

Where can I find "ACPI people" ?

Thanks.

Re: Touchpad errors

[Sid Boyce]

Dmitry Torokhov wrote:
> 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?
> 
It does not boot with SuSE 9.3 default kernel, 2.6.13-rc3 or 
2.6.13-rc4-git4, locks up after an initial message with a blank screen.
Acer 1501LCe x86_64 laptop.
Regards
Sid.
-- 
Sid Boyce ... Hamradio License G3VBV, Keen licensed Private Pilot
Retired IBM Mainframes and Sun Servers Tech Support Specialist
Microsoft Windows Free Zone - Linux used for all Computing Tasks

Re: Touchpad errors

[Sid Boyce]

Lee Revell wrote:
> On Wed, 2005-08-03 at 00:14 +0400, Dmitrij Bogush wrote:
> 
>>This happens when some software check battery state or current cpu
>>rate too often.
> 
> 
> Acer laptops are notorious for buggy SMM implementations that disable
> interrupts for many timer ticks.  Does it work any better with HZ=100?
> 
> Lee
> 
> 
> 

The problem, initially at least, doesn't seem as sever at HZ=100, 18 
occurrences in 3 mins 30 seconds.
Regards
Sid.
-- 
Sid Boyce ... Hamradio License G3VBV, Keen licensed Private Pilot
Retired IBM Mainframes and Sun Servers Tech Support Specialist
Microsoft Windows Free Zone - Linux used for all Computing Tasks