public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jordan Crouse <jordan@cosmicpenguin.net>
To: Harald Dunkel <harald.dunkel@t-online.de>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.27.7 built for Geode: Clock drift
Date: Fri, 05 Dec 2008 10:16:30 -0700	[thread overview]
Message-ID: <493961EE.6000002@cosmicpenguin.net> (raw)
In-Reply-To: <49358017.7080009@t-online.de>

Harald Dunkel wrote:
> Hi folks,
> 
> If I build a kernel for AMD Geode, then I see a clock drift of appr.
> 30 min. to 1 hour per day. If I build the same kernel for i486, then
> the clock drift is gone. Running ntp makes no difference.
> 
> Hardware is a Linutop PC. /proc/cpuinfo says
> 
> processor       : 0
> vendor_id       : AuthenticAMD
> cpu family      : 5
> model           : 10
> model name      : Geode(TM) Integrated Processor by AMD PCS
> stepping        : 2
> cpu MHz         : 0.000
> cache size      : 128 KB
> fdiv_bug        : no
> hlt_bug         : no
> f00f_bug        : no
> coma_bug        : no
> fpu             : yes
> fpu_exception   : yes
> cpuid level     : 1
> wp              : yes
> flags           : fpu de pse tsc msr cx8 sep pge cmov clflush mmx mmxext 3dnowext 3dnow
> bogomips        : 429.05
> clflush size    : 32
> power management:
> 
> BTW, the CPU is running with 500 MHz (AFAIK). 0.000 MHz is surely not
> correct. /proc/cpuinfo reports the same for both kernels.

Hmm - we've heard reports of this before, but nothing came of it.  I 
would be interested in a chance to debug it this time.

Please try turning off CONFIG_GEODE_MFGPT_TIMER=y and try again.  Also, 
try something in the 2.6.28 family to rule out fixes in the timer subsystem.

Thanks,
Jordan

  reply	other threads:[~2008-12-05 17:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-02 18:36 2.6.27.7 built for Geode: Clock drift Harald Dunkel
2008-12-05 17:16 ` Jordan Crouse [this message]
2008-12-06 14:12   ` Harald Dunkel
2008-12-06 14:21   ` Harald Dunkel
2008-12-06 16:45     ` Jordan Crouse
2008-12-07  5:02   ` Harald Dunkel
2008-12-05 21:40 ` john stultz
2008-12-06  6:09   ` Harald Dunkel
2008-12-09  2:14     ` john stultz
2008-12-09 15:09       ` Jordan Crouse

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=493961EE.6000002@cosmicpenguin.net \
    --to=jordan@cosmicpenguin.net \
    --cc=harald.dunkel@t-online.de \
    --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