public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitrij Bogush <dmitrij.bogush-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Dmitrij Bogush
	<dmitrij.bogush-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Touchpad problem on 15XX Acer Aspire laptops.
Date: Sat, 13 Aug 2005 06:03:52 +0400	[thread overview]
Message-ID: <2ac89c7005081219032e131fd4@mail.gmail.com> (raw)
In-Reply-To: <20050812075251.GA14465-qYCAlGQNbcFrdx17CPfAsdBPR1lH4CV8@public.gmane.org>

Hi.

Patch that I find at "
http://bugzilla.kernel.org/attachment.cgi?id=5599&action=view " does
not make any good thing. With this patch I still see log messages like
"Many lost ticks. Cheking if cpu frequency changed.." and "Touchpad
lost sync at byte N". And one strange thing against this patch:
keyboard lags too (I mean if for example "Q" is pressed and battery
state checked at same time I get
"qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq" in console)
With patch " http://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/patches/release/2.6.13/acpi-20050729-2.6.13-rc6.diff.bz2
" I don't more see any messages at all, only one-second-freezes like
with clean rc6.

2005/8/12, Yu, Luming <luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>:
> On 2005.08.03 05:12:35 +0400, Dmitrij Bogush wrote:
> > Hi.
> >
> > Someone Dmitry Torokhov on LKML told me to contact ACPI mailing list
> > with this problem.
> >
> > Touchpad goes crazy then programs like Kpowersave or Gkrellm check
> > battery state or current cpu frequency.
> >
> >  With 2.6.11.4 in dmesg I see this:
> >
> > psmouse.c: TouchPad at isa0060/serio4/input0 - driver resynched.
> > psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 4
> >
> > With latest 2.6.13-rc5 kernel I get this:
> >
> > warning: many lost ticks.
> > Your time source seems to be instable or some driver is hogging interupts
> > rip handler_IRQ_event+0x20/0x60
> >
> > With 2.6.13-rc5 touchpad freezes for a second, do not goese crazy like
> > with 2.6.11.
> >
> > Thanks.
> >
> Please test linux-2.6.13-rc6 with patch filed at bug 3851 , Please try both
> ec_burst=0 and ec_burst=1.
> Thanks,
> Luming
> 


-- 
Best Regards,
Dmitrij A Bogush.


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

  parent reply	other threads:[~2005-08-13  2:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-03  1:12 Touchpad problem on 15XX Acer Aspire laptops Dmitrij Bogush
     [not found] ` <2ac89c700508021812208f23d6-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2005-08-12  7:52   ` Yu, Luming
     [not found]     ` <20050812075251.GA14465-qYCAlGQNbcFrdx17CPfAsdBPR1lH4CV8@public.gmane.org>
2005-08-13  2:03       ` Dmitrij Bogush [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-08-13  2:43 Yu, Luming

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=2ac89c7005081219032e131fd4@mail.gmail.com \
    --to=dmitrij.bogush-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    /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