From: Andi Kleen <ak@suse.de>
To: Alistair John Strachan <s0348365@sms.ed.ac.uk>
Cc: linux-kernel@vger.kernel.org, cpufreq@lists.linux.org.uk
Subject: Re: 2.6.16-rc2, x86-64, CPU hotplug failure
Date: Mon, 13 Feb 2006 10:18:06 +0100 [thread overview]
Message-ID: <200602131018.06549.ak@suse.de> (raw)
In-Reply-To: <200602130230.41120.s0348365@sms.ed.ac.uk>
On Monday 13 February 2006 03:30, Alistair John Strachan wrote:
> Hi,
>
> In an attempt to play with ACPI S3 on my Athlon 64 X2 3800+, I recompiled
> 2.6.16-rc2 with CPU hotplug and ACPI sleep state support. I experienced
> multiple crashes and oopsen, which I quickly discovered were the result of
> bringing at least one CPU back online.
Yes, known problem. They seem to be related to the powernow driver. Does
it work if you don't compile CPUFREQ in?
-Andi
prev parent reply other threads:[~2006-02-13 9:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-13 2:30 2.6.16-rc2, x86-64, CPU hotplug failure Alistair John Strachan
2006-02-13 7:05 ` Zwane Mwaikambo
2006-02-13 10:06 ` Alistair John Strachan
2006-02-13 9:18 ` Andi Kleen [this message]
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=200602131018.06549.ak@suse.de \
--to=ak@suse.de \
--cc=cpufreq@lists.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=s0348365@sms.ed.ac.uk \
/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