From: Georg Schild <dangertools@gmx.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Losing too many ticks! .... on a VIA epia board
Date: Tue, 14 Sep 2004 11:53:16 +0200 [thread overview]
Message-ID: <4146BF8C.20309@gmx.net> (raw)
In-Reply-To: <4146A09A.9010207@zensonic.dk>
> Losing some ticks... checking if CPU frequency changed.
> Losing some ticks... checking if CPU frequency changed.
> Losing too many ticks!
> TSC cannot be used as a timesource. Possible reasons for this are:
> You're running with Speedstep,
> You don't have DMA enabled for your hard disk (see hdparm),
> Incorrect TSC synchronization on an SMP system (see dmesg).
> Falling back to a sane timesource now.
>
>
> Furthermore editors like jed and emacs takes forever to start. A "strace
> emacs /somefile" shows that it hangs in a poll right after gettimeofday.
>
> Any clues to what is wrong and how I go about fixing it?!
>
> Regards Thomas, Denmark
>
I don't have a clue but the same problem on an amd64 system. I am
running a 64bit 2.6.9-rc1-mm4 kernel on my machine and if i add the boot
parameter report_lost_ticks it reports the same messages as your
machine. Since 2.6.7 there is this parameter, before the lost ticks
where reported all the time. I always thought that this is a 64bit
problem because i have heard from others which have this problem too.
Why are we loosing ticks? On my system it happens almost when an acpi
event occurs. I know that they aren't reported anymore but I don't like
the thing that my processor (or timesource) looses something.
Georg Schild
next prev parent reply other threads:[~2004-09-14 10:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-14 7:41 Losing too many ticks! .... on a VIA epia board Thomas S. Iversen
2004-09-14 9:53 ` Georg Schild [this message]
2004-09-14 13:57 ` Thomas S. Iversen
2004-09-15 10:42 ` Georg Schild
2004-09-14 21:52 ` Thomas S. Iversen
2004-09-15 8:57 ` Prakash K. Cheemplavam
2004-09-15 9:02 ` Thomas S. Iversen
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=4146BF8C.20309@gmx.net \
--to=dangertools@gmx.net \
--cc=linux-kernel@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