linux-kernel - Re: 2.6.27.7 built for Geode: Clock drift

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <493961EE.6000002@cosmicpenguin.net>
Date:	Fri, 05 Dec 2008 10:16:30 -0700
From:	Jordan Crouse <jordan@...micpenguin.net>
To:	Harald Dunkel <harald.dunkel@...nline.de>
CC:	Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.27.7 built for Geode: Clock drift

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/