From: Mark van Dijk <lists+xen@internecto.net>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen-devel@lists.xen.org
Subject: Re: Kernel crash with acpi_processor, cpu_idle and intel_idle =y
Date: Thu, 26 Jul 2012 02:25:27 +0200 [thread overview]
Message-ID: <20120726022527.4d3f6e4a@internecto.net> (raw)
In-Reply-To: <20120723142025.GB793@phenom.dumpdata.com>
Hi Konrad,
> > When I set CONFIG_ACPI_PROCESSOR, CONFIG_CPU_IDLE and
> > CONFIG_INTEL_IDLE to y then I cannot boot Xen; there is a crash. If
> > I turn CONFIG_INTEL_IDLE off then the boot goes well and, after
> > dom0 has booted, xenpm works and gives some sane output, see below.
> > I have tested this with kernels 3.2 to 3.4.6.
> >
> > Is it impossible to use INTEL_IDLE with Xen? If this is a known
> > issue then maybe someone can add info to the INTEL_IDLE help text
> > in the kernel configuration...
>
> Could be - without a serial crash it is hard to figure out.
Alright, I will enable INTEL_IDLE again so that I can report the crash
message. Won't be now but it will be within the next few days.
> Why do you want to use the intel idle driver? Can't you use
> the xen-acpi-processor driver which does the job of uploading
> the power management data to the hypervisor.
>
> (CONFIG_XEN_ACPI_PROCESSOR is the option you need to have enabled).
I just checked - I have enabled this option. It is in Device Drivers ->
Xen driver support which did confuse me somewhat, partially because the
rest of the ACPI options are under 'Power management and ACPI
options', also because the options look alike so much, I suppose
fatigue kicked in. :)
Anyway, It seems that CONFIG_XEN_ACPI_PROCESSOR depends on
ACPI_PROCESSOR, see below.
To answer your question about why I want to use the intel idle driver.
Actually I don't want/need to use it per se.. I simply thought it was
the logical choice to enable it in order to be able to use Intel
specific idle instructions.
> > I am using this on a dual CPU motherboard, it has two Xeon W3530
> > CPUs (i.e. family 6, model 26, stepping 5). I have also tested this
> > with a single-CPU Core2 Quad Q6600 and the same situation occurs
> > here, but the below output is of the W3530 Xeon system.
> >
> > While I'm not that familiar with CPUidle, one thing that seems to be
> > not right is that the maximum idle state here is C3 while the
> > processor should be able to reach as far as C7.
>
> Right, it won't unless you don't compile acpi_pad
> (CONFIG_ACPI_PROCESSOR). Is # CONFIG_ACPI_PROCESSOR is not set" in
> your .config?
No, and this is where I start to wonder. I have built in the CPUFREQ
drivers and the kernel help text says that when this is the case,
CONFIG_XEN_ACPI_PROCESSOR must be Y as well. For this to work I have to
set CONFIG_ACPI_PROCESSOR to Y because:
XEN_ACPI_PROCESSOR [=y]
Depends on: XEN [=y] && X86 [=y] && ACPI_PROCESSOR [=y] && CPU_FREQ [=y]
The full .config is here:
http://pastebin.com/36a2tVYj
What I am after: cpu scheduling (xenpm set-cpufreq-governor) and
maximum idle states. But you can see that I am not as knowledgable as
yourself, so further hints or requests for debugging are welcome (the
INTEL_IDLE boot crash message will be posted when I am able to fiddle
with the kernel again) and thanks so far for your answers.
Mark
next prev parent reply other threads:[~2012-07-26 0:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-22 16:16 Kernel crash with acpi_processor, cpu_idle and intel_idle =y Mark van Dijk
2012-07-23 14:20 ` Konrad Rzeszutek Wilk
2012-07-26 0:25 ` Mark van Dijk [this message]
2012-07-26 7:15 ` Jan Beulich
2012-07-26 14:05 ` Konrad Rzeszutek Wilk
2012-07-26 14:57 ` Jan Beulich
2012-07-26 14:55 ` Konrad Rzeszutek Wilk
2012-07-28 12:55 ` Mark van Dijk
2012-07-30 7:45 ` Jan Beulich
2012-07-31 11:58 ` Mark van Dijk
2012-07-31 13:42 ` Konrad Rzeszutek Wilk
2012-07-31 13:40 ` Konrad Rzeszutek Wilk
2012-07-31 21:50 ` Mark van Dijk
2012-07-31 23:42 ` Konrad Rzeszutek Wilk
2012-07-31 23:59 ` Mark van Dijk
2012-07-31 23:55 ` Konrad Rzeszutek Wilk
2012-08-01 0:25 ` Mark van Dijk
2012-07-23 14:28 ` Jan Beulich
2012-07-26 0:30 ` Mark van Dijk
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=20120726022527.4d3f6e4a@internecto.net \
--to=lists+xen@internecto.net \
--cc=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xen.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;
as well as URLs for NNTP newsgroup(s).