All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Heyse <m.heyse@designassembly.de>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: Giacomo Di Ciocco <admin@nectarine.info>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.0 "Losing too many ticks!"
Date: Thu, 25 Dec 2003 03:33:09 +0100	[thread overview]
Message-ID: <3FEA4C65.2090903@designassembly.de> (raw)
In-Reply-To: <20031224185248.GG27687@holomorphy.com>

William Lee Irwin III wrote:

> This is not particularly harmful. It just means the kernel has detected
> some variation in the processor's clock speed and is using a time source
> that doesn't change speed along with the processor's clock speed.

I had the same problem with an AMD K6-2 on VIA Aladdin V chipset, and it 
WAS harmful, time source not sane at all, because the clock went at 
about half speed.

What worked for me: using Andrew Morton's kernel, it includes a 
via-tsc-fix.patch, now everything's all right.

Greetings,

Michael

  reply	other threads:[~2003-12-25  2:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-24 18:49 2.6.0 "Losing too many ticks!" Giacomo Di Ciocco
2003-12-24 18:52 ` William Lee Irwin III
2003-12-25  2:33   ` Michael Heyse [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-12-24 19:12 2.6.0 "Losing too many ticks" Giacomo Di Ciocco
2003-12-25  3:05 2.6.0 "Losing too many ticks!" Albert Cahalan
2003-12-25 16:02 ` Giacomo Di Ciocco
     [not found] ` <20031225161748.GA31564@tsunami.ccur.com>
2003-12-25 18:14   ` Giacomo Di Ciocco
2003-12-25 18:05     ` Albert Cahalan

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=3FEA4C65.2090903@designassembly.de \
    --to=m.heyse@designassembly.de \
    --cc=admin@nectarine.info \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wli@holomorphy.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.