[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20081020202529.GE21041@cosmic.amd.com>
Date: Mon, 20 Oct 2008 14:25:29 -0600
From: Jordan Crouse <jordan.crouse@....com>
To: Alok Kataria <alokkataria1@...il.com>
CC: Antipov Dmitry <dmantipov@...dex.ru>, linux-kernel@...r.kernel.org,
akataria@...are.com
Subject: Re: 2.6.27: 0 MHz CPU and wrong system time on AMD Geode system
On 17/10/08 15:17 -0700, Alok Kataria wrote:
> On Thu, Oct 16, 2008 at 9:48 PM, Antipov Dmitry <dmantipov@...dex.ru> wrote:
> > Jordan Crouse wrote:
> >
> >> Could you try a 2.6.26 kernel? That will confirm that this is a new
> >> addition to 2.6.27.
> >
> > Both 2.6.26 and 2.6.26.6 looks good (with CONFIG_GEODE_MFGPT_TIMER=y).
>
> Can you try the attached debug patch, it puts a printk message and
> will let us know what exaclty is failing during the calibration
> process.
> There were some major changes in the 2.6.27 cycle related to tsc calibration.
> Apart from the unification for 32 and 64bit, some checks were added in
> the code to make the calibration process more robust, maybe this
> specific machine is more prone to SMI's than other, as a result the
> checks are a little to harsh for this one.
>
> Along with the dmesg with this patch, could you also let us know how
> much is the frequency that the (2.6.26) kernel calibrates and what the
> actual freuqency is on that box ?
I just booted with 2.6.27.1 with high res timers on, and I can't recreate
on a generic Geode box. The only difference is that my system doesn't
have any MFGPT timers available, but that shouldn't matter if you have
CONFIG_GEODE_MFGPT_TIMER turned off.
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