From: "Alok Kataria" <alokkataria1@gmail.com>
To: "Antipov Dmitry" <dmantipov@yandex.ru>
Cc: 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: Fri, 17 Oct 2008 15:17:39 -0700 [thread overview]
Message-ID: <35f686220810171517y6632b4b2p3d251d43753eb3d6@mail.gmail.com> (raw)
In-Reply-To: <673951224218937@webmail87.yandex.ru>
[-- Attachment #1: Type: text/plain, Size: 1194 bytes --]
On Thu, Oct 16, 2008 at 9:48 PM, Antipov Dmitry <dmantipov@yandex.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 ?
Thanks,
Alok
>
> Dmitry
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: debug_tsc_calibrate.patch --]
[-- Type: text/x-patch; name=debug_tsc_calibrate.patch, Size: 410 bytes --]
Index: linux-2.6/arch/x86/kernel/tsc.c
===================================================================
--- linux-2.6.orig/arch/x86/kernel/tsc.c 2008-10-17 14:56:23.000000000 -0700
+++ linux-2.6/arch/x86/kernel/tsc.c 2008-10-17 15:01:38.000000000 -0700
@@ -163,6 +163,8 @@
pitcnt++;
}
+ printk("DEBUG: pitcnt %d, tscmin %lu, tscmax %lu\n",
+ pitcnt, tscmin, tscmax);
/*
* Sanity checks:
*
next prev parent reply other threads:[~2008-10-17 22:17 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 [this message]
2008-10-20 20:23 ` Lennart Sorensen
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=35f686220810171517y6632b4b2p3d251d43753eb3d6@mail.gmail.com \
--to=alokkataria1@gmail.com \
--cc=akataria@vmware.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®