mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Bug 827] New: System time runs too fast.
Date: 18 Jun 2003 20:13:09 +0200	[thread overview]
Message-ID: <1055959989.586.4.camel@teapot.felipe-alfaro.com> (raw)
In-Reply-To: <10940000.1055947324@[10.10.2.4]>

On Wed, 2003-06-18 at 16:42, Martin J. Bligh wrote:
>            Summary: System time runs too fast.
>     Kernel Version: 2.5.72
>             Status: NEW
>           Severity: normal
>              Owner: bugme-janitors@lists.osdl.org
>          Submitter: ialiashkevich@epo.org
> 
> 
> Distribution:
> 
> Hardware Environment:
> Notebook Maxdata Eco 3000X
> Processor: P4 2Gz
> Chipset: SIS650
> 
> Software Environment:
> RedHat 8.0 + kernel 2.5.70
> RedHat 9.0 + kernel 2.5.72
> kernels were built by gcc 3.2.3 using default .config from arch/i386
> 
> Problem Description:
> System time runs at least twice faster than necessary.
> As a result have problems with keyboard timings:
>    very short delay before repeat mode and very fast repeat rate
> problems with mouse:
>    very fast double-click speed
>    
> Steps to reproduce:
>   buld, install kernel and restart :)

BTW, are you using CPU frequency scaling? While playing with my P4's CPU
frequency scaling, lowering the CPU frequency below a threshold
frequency value (below 1.4GHz approx.), the system starts acting
erratically: the keyboard generates event at twice or three times the
normal speed iiitttsss nnneeeaaarrrlllyyy iiimmmpppooosssiiibbbllleee to
type anything. The system clock starts skewing at a really fast pace and
the mouse is unusable. The only solution is returning the CPU frequency
to a higher value.


      reply	other threads:[~2003-06-18 17:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-18 14:42 Martin J. Bligh
2003-06-18 18:13 ` Felipe Alfaro Solana [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=1055959989.586.4.camel@teapot.felipe-alfaro.com \
    --to=felipe_alfaro@linuxmail.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@aracnet.com \
    /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

all inboxes | Powered by JetHome®