From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: Alok Kataria <alokkataria1@gmail.com>
Cc: Antipov Dmitry <dmantipov@yandex.ru>,
linux-kernel@vger.kernel.org,
Jordan Crouse <jordan.crouse@amd.com>,
akataria@vmware.com
Subject: Re: 2.6.27: 0 MHz CPU and wrong system time on AMD Geode system
Date: Mon, 20 Oct 2008 16:23:57 -0400 [thread overview]
Message-ID: <20081020202357.GF22851@csclub.uwaterloo.ca> (raw)
In-Reply-To: <35f686220810171517y6632b4b2p3d251d43753eb3d6@mail.gmail.com>
On Fri, Oct 17, 2008 at 03:17:39PM -0700, Alok Kataria wrote:
> 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.
I recently had to disable the timer generating an SMI on our platform,
because it would cause FIFO overflows on serial ports and other
infrequent problems. SMM/SMI is just a pain in the rear.
I haven't tried 2.6.27 yet, but have not had issues with 2.6.26 so far
(other than it seemingly breaking the SC1200's ide controller with
certain compact flash cards which I am still trying to track down, but
that isn't a Geode LX problem, that's a Geode SC1200 problem).
--
Len Sorensen
next prev parent reply other threads:[~2008-10-20 20:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-17 4:48 Antipov Dmitry
2008-10-17 22:17 ` Alok Kataria
2008-10-20 20:23 ` Lennart Sorensen [this message]
2008-10-20 20:25 ` Jordan Crouse
-- strict thread matches above, loose matches on Subject: below --
2008-10-15 6:39 Antipov Dmitry
2008-10-15 16:21 ` Jordan Crouse
2008-10-16 11:31 ` Dmitry Antipov
2008-10-16 14:39 ` 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=20081020202357.GF22851@csclub.uwaterloo.ca \
--to=lsorense@csclub.uwaterloo.ca \
--cc=akataria@vmware.com \
--cc=alokkataria1@gmail.com \
--cc=dmantipov@yandex.ru \
--cc=jordan.crouse@amd.com \
--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
all inboxes | Powered by JetHome®