From: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
To: smurf@smurf.noris.de
Cc: Matthias Urlichs <smurf@smurf.noris.de>,
linux-kernel@vger.kernel.org, johnstul@us.ibm.com,
torvalds@osdl.org, bunk@stusta.de, lethal@linux-sh.org,
hirofumi@mail.parknet.co.jp, akpm@osdl.org
Subject: Re: REGRESSION: the new i386 timer code fails to sync CPUs
Date: Mon, 24 Jul 2006 08:52:01 -0700 [thread overview]
Message-ID: <20060724085201.A6517@unix-os.sc.intel.com> (raw)
In-Reply-To: <20060723053755.0aaf9ce0.akpm@osdl.org>; from akpm@osdl.org on Sun, Jul 23, 2006 at 05:37:55AM -0700
On Sun, Jul 23, 2006 at 05:37:55AM -0700, Andrew Morton wrote:
> On Sun, 23 Jul 2006 14:08:29 +0200
> Matthias Urlichs <smurf@smurf.noris.de> wrote:
> > Interestingly, CPU0/1 gets 6000 bogomips while CPU2/3 only reaches 5600 ..?
> > (That happens with both kernels.) I do wonder why, and whether this has any
> > bearing on the current problem.
>
> I wouldn't expect it to matter, unless the TSCs are running at different
> speeds or something.
Matthias, Can you send us the /proc/cpuinfo output of your system?
>From your config it looks like CPU_FREQ is disabled. Perhaps, can you try with
CPU_FREQ enabled in your config and see if you see the same issue?
thanks,
suresh
next prev parent reply other threads:[~2006-07-24 16:12 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-22 23:36 REGRESSION: the new i386 timer code fails to sync CPUs Matthias Urlichs
2006-07-23 0:36 ` Andrew Morton
2006-07-23 8:16 ` Matthias Urlichs
2006-07-23 11:46 ` Andrew Morton
2006-07-23 12:08 ` Matthias Urlichs
2006-07-23 12:37 ` Andrew Morton
2006-07-23 12:58 ` Matthias Urlichs
2006-07-24 15:52 ` Siddha, Suresh B [this message]
2006-07-24 15:58 ` john stultz
2006-07-24 17:17 ` Matthias Urlichs
2006-07-24 17:51 ` Andi Kleen
2006-07-24 20:54 ` john stultz
2006-07-30 9:03 ` Andrew Morton
2006-07-30 9:49 ` Matthias Urlichs
2006-07-30 20:10 ` Andi Kleen
2006-07-30 20:55 ` Andrew Morton
2006-07-30 21:13 ` Matthias Urlichs
2006-07-30 21:20 ` Arjan van de Ven
2006-07-30 21:55 ` Matthias Urlichs
2006-08-01 1:47 ` Siddha, Suresh B
2006-08-01 3:14 ` Matthias Urlichs
2006-07-30 21:57 ` Andi Kleen
2006-07-30 22:28 ` Matthias Urlichs
2006-07-31 14:24 ` Matthias Urlichs
2006-07-24 17:39 ` Andi Kleen
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=20060724085201.A6517@unix-os.sc.intel.com \
--to=suresh.b.siddha@intel.com \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=hirofumi@mail.parknet.co.jp \
--cc=johnstul@us.ibm.com \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=smurf@smurf.noris.de \
--cc=torvalds@osdl.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