public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Sergio Monteiro Basto <sergio@sergiomb.no-ip.org>
To: Lex Neva <acpi@lexneva.name>
Cc: linux-acpi@vger.kernel.org
Subject: Re: C2 and C3 processor states cause mouse desynchronization
Date: Tue, 24 Apr 2007 01:50:43 +0100	[thread overview]
Message-ID: <1177375843.3689.15.camel@monteirov> (raw)
In-Reply-To: <Pine.LNX.4.64.0704222237480.25154@lexneva.name>

[-- Attachment #1: Type: text/plain, Size: 1051 bytes --]

On Sun, 2007-04-22 at 22:57 -0400, Lex Neva wrote:
> So, the questions I have:
> 
> Is this a problem anyone's seen before?
> 
> Is this a bug?  If so, is it in linux-ACPI or psmouse (or something
> else)?
> 
> Is there anything I can do to get my power savings and still make the
> mouse 
> driver happy?
> 
> Is there any chance that I can work with the linux-ACPI developers to
> get a 
> fix produced?
> 

Well I am not a kernel hacker either but 
what give you ? 
cat /sys/devices/system/clocksource/clocksource0/available_clocksource
cat /sys/devices/system/clocksource/clocksource0/current_clocksource

and boot with parameter: report_lost_ticks

and boot with parameter: notsc ( try first report_lost_ticks if you got
lost ticket than boot with both notsc and report_lost_ticks )

cat /proc/interrupts 
At MNI got any value, different than zero ?

I got all my ansync computer problems resolved at 2.6.21-rc5, but I had
more problems that just a mouse desynchronization 
 

Best regards , 
-- 
Sérgio M.B.

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 2192 bytes --]

      reply	other threads:[~2007-04-24  0:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-23  2:57 C2 and C3 processor states cause mouse desynchronization Lex Neva
2007-04-24  0:50 ` Sergio Monteiro Basto [this message]

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=1177375843.3689.15.camel@monteirov \
    --to=sergio@sergiomb.no-ip.org \
    --cc=acpi@lexneva.name \
    --cc=linux-acpi@vger.kernel.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