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: <20081015162143.GA19397@cosmic.amd.com>
Date:	Wed, 15 Oct 2008 10:21:43 -0600
From:	Jordan Crouse <jordan.crouse@....com>
To:	Antipov Dmitry <dmantipov@...dex.ru>
CC:	linux-kernel@...r.kernel.org
Subject: Re: 2.6.27: 0 MHz CPU and wrong system time on AMD Geode system

On 15/10/08 10:39 +0400, Antipov Dmitry wrote:
> After updating the kernel to 2.6.27 from 2.6.25.4, my system time goes wrong and
> CPU becomes 0 MHz (as shown by /proc/cpuinfo), probably due to these issues:
> 
> TSC: Unable to calibrate against PIT
> TSC: No reference (HPET/PMTIMER) available
> Marking TSC unstable due to could not calculate TSC khz
> 
> The hardware is http://www.fit-pc.com/new/fit-pc-1-0-specifications.html,
> and the base system is Fedora 9.
> 
> More details: 2.6.25.4 .config: http://78.153.153.8/tmp/config-2.6.25.4.txt
>               2.6.25.4 boot messages: http://78.153.153.8/tmp/boot-2.6.25.4.txt
>               2.6.27 .config: http://78.153.153.8/tmp/config-2.6.27.txt
>               2.6.27 boot messages: http://78.153.153.8/tmp/boot-2.6.27.txt

Hmmm - this is an interesting regression.  Please remove
CONFIG_GEODE_MFGPT_TIMER=y from your 2.6.27 kernel and see if the
problem goes away.  I have been running 2.6.26.5 on my system with no
problems, but I'm embarrassed to admit that I haven't run anything
newer in a while.  

Jordan
-- 
Jordan Crouse
Systems Software Development Engineer 
Advanced Micro Devices, Inc.

--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ