From: Frank van Maarseveen <frankvm@frankvm.com>
To: Nathan Becker <nbecker@physics.ucsb.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: lost ticks and Hangcheck
Date: Tue, 30 Aug 2005 15:47:43 +0200 [thread overview]
Message-ID: <20050830134743.GA26890@janus> (raw)
In-Reply-To: <Pine.LNX.4.63.0508182351460.6338@claven.physics.ucsb.edu>
On Fri, Aug 19, 2005 at 12:41:07AM -0700, Nathan Becker wrote:
> Hi,
>
> I'm running kernel 2.6.12.5 with x86_64 target on an AMD X2 4800+ and
> Gigabyte GA-K8NXP-SLI motherboard (bios version F8). I'm having a problem
> with lost clock ticks. The dmesg says
>
> warning: many lost ticks.
> Your time source seems to be instable or some driver is hogging interupts
>
> Also if I enable hangcheck, then I get a huge number of Hangcheck messages
> in dmesg.
I get a lot of "kernel: Hangcheck: hangcheck value past margin!" messages
from 2.6.13-rc7 on AMD64 X2 3800+ and Asus A8V deluxe motherboard. No lost
ticks messages however.
>
> The main other symptom is that the system clock runs fast and
> inaccurately. It seems to run more inaccurately when I'm using the CPU,
> and be basically OK when idling.
That seems to be the case here too: clock runs too fast under heavy load
(burn-in tests involving kernel builds and large disk copies).
--
Frank
next prev parent reply other threads:[~2005-08-30 13:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-19 7:41 lost ticks and Hangcheck Nathan Becker
2005-08-19 9:45 ` Kurt Wall
2005-08-20 0:22 ` Nathan Becker
2005-08-20 0:34 ` john stultz
2005-08-20 9:50 ` Nathan Becker
2005-08-30 13:47 ` Frank van Maarseveen [this message]
2005-09-04 11:39 ` 2.6.13 SMP on Athlon X2: nanosleep returning waay to soon, clock_gettime(CLOCK_REALTIME...) proceeding too fast Frank van Maarseveen
2005-09-04 14:27 ` Daniel Jacobowitz
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=20050830134743.GA26890@janus \
--to=frankvm@frankvm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nbecker@physics.ucsb.edu \
/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.