From: Pavel Machek <pavel@suse.cz>
To: "shin, jacob" <jacob.shin@amd.com>
Cc: "Deguara, Joachim" <joachim.deguara@amd.com>,
Andi Kleen <ak@suse.de>,
"Langsdorf, Mark" <mark.langsdorf@amd.com>,
discuss@x86-64.org, linux-kernel@vger.kernel.org,
cpufreq@lists.linux.org.uk
Subject: Re: [discuss] Re: [PATCH] Allow all Opteron processors to change pstate at same time
Date: Thu, 13 Jul 2006 13:06:05 +0000 [thread overview]
Message-ID: <20060713130604.GC8230@ucw.cz> (raw)
In-Reply-To: <B3870AD84389624BAF87A3C7B831499302935A76@SAUSEXMB2.amd.com>
Hi!
> > Here are the further findings after letting the machine toggle between
> > 1GHz and 2.2Ghz every two seconds for roughly 24 hours. Unfortunately
> > there is an oops after bringing CPU2 online and CPU3 will not come
> > online. Still the differences in TSC are not bad:
>
> Can I get more information on how to reproduce the Oops? Kernel version?
> .config? your hardware?
>
> I have run basic set of CPU Hotplug on/offline tests, and I could not
> reproduce it..
Can you run two such tests *in parallel*? That seemed to break it
really quickly.
Pavel
--
Thanks for all the (sleeping) penguins.
next prev parent reply other threads:[~2006-07-13 13:06 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-12 16:11 [discuss] Re: [PATCH] Allow all Opteron processors to change pstate at same time shin, jacob
2006-07-12 16:14 ` Langsdorf, Mark
2006-07-13 13:06 ` Pavel Machek [this message]
2006-07-13 14:32 ` Joachim Deguara
2006-07-16 1:56 ` Pavel Machek
2006-07-17 7:37 ` Joachim Deguara
2006-07-20 15:59 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2006-07-13 13:37 Bhavana Nagendra
2006-07-06 20:31 Mark Langsdorf
2006-07-07 12:10 ` Andi Kleen
2006-07-07 17:36 ` [discuss] " Langsdorf, Mark
2006-07-10 12:45 ` Joachim Deguara
2006-07-10 13:02 ` Joachim Deguara
2006-07-11 12:55 ` Joachim Deguara
2006-07-11 13:07 ` Andi Kleen
2006-07-11 13:14 ` Arjan van de Ven
2006-07-11 16:15 ` Alan Cox
2006-07-11 16:01 ` Arjan van de Ven
2006-07-11 16:04 ` Andi Kleen
2006-07-11 13:31 ` Langsdorf, Mark
2006-07-11 13:34 ` Arjan van de Ven
2006-07-11 13:51 ` Andi Kleen
2006-07-12 14:06 ` Joachim Deguara
2006-07-12 14:54 ` Andi Kleen
2006-07-25 21:47 ` Langsdorf, Mark
2006-07-26 11:31 ` Joachim Deguara
2006-07-26 16:42 ` Langsdorf, Mark
2006-07-26 16:54 ` Andi Kleen
2006-07-26 18:34 ` Langsdorf, Mark
2006-07-26 18:53 ` 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=20060713130604.GC8230@ucw.cz \
--to=pavel@suse.cz \
--cc=ak@suse.de \
--cc=cpufreq@lists.linux.org.uk \
--cc=discuss@x86-64.org \
--cc=jacob.shin@amd.com \
--cc=joachim.deguara@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.langsdorf@amd.com \
/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