From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Mark van Dijk <lists+xen@internecto.net>, xen-devel@lists.xen.org
Subject: Re: Kernel crash with acpi_processor, cpu_idle and intel_idle =y
Date: Tue, 31 Jul 2012 09:40:55 -0400 [thread overview]
Message-ID: <20120731134054.GD4789@phenom.dumpdata.com> (raw)
In-Reply-To: <501657C70200007800091357@nat28.tlf.novell.com>
On Mon, Jul 30, 2012 at 08:45:43AM +0100, Jan Beulich wrote:
> >>> On 28.07.12 at 14:55, Mark van Dijk <lists+xen@internecto.net> wrote:
> >> > > So.. in that case make sure you have XEN_ACPI_PROCESSOR=y and
> >> > > "CONFIG_INTEL_IDLE is not set" and that should do it.
> >> >
> >> > Didn't he say that with INTEL_IDLE disabled things work (perhaps
> >> > in a limited way, but at least don't crash)? My understanding is
> >> > that things should work even with it enabled, and I was under the
> >> > impression that you had already taken care of disabling cpuidle
> >> > and cpufreq in the kernel when running on Xen...
> >>
> >> So did I - both of those (cpufreq and cpuidle) are disabled.
> >>
> >> Mark, any chance you can collect the serial output when it crashes
> >> please? Actually, can you get the whole bootup log with 'loglevel=8
> >> debug' on the Linux command line?
> >>
> >
> > The sad part is that I don't have physical access to the box, the good
> > part is that I do have KVM and IPMI (SOL) access.
> >
> > This is what I could capture:
> >
> > http://i.imgur.com/t66FM.png
>
> The first thing intel_idle_init() does is check
> boot_option_idle_override, and I thought this got forced to
> something other than IDLE_NO_OVERRIDE by the Xen code.
Yeah, by me thinking everything is peachy and that override is
no longer needed :-(
> But at least in the current kernel that doesn't seem to be
> the case anymore, and thus I suppose that it's dying on the
> subsequent
>
> retval = cpuidle_register_driver(&intel_idle_driver);
> if (retval) {
> printk(KERN_DEBUG PREFIX "intel_idle yielding to %s",
> cpuidle_get_driver()->name);
> return retval;
> }
>
> since cpuidle_get_driver() is presumably returning NULL (after
> all xen_arch_setup() does call disable_cpuidle()).
Duh! That is easy enough to fix. Mark, can you please try testing with
this patch (and obviously enable the CONFIG_INTEL_IDLE)
diff --git a/drivers/idle/intel_idle.c b/drivers/idle/intel_idle.c
index d0f59c3..46a9884 100644
--- a/drivers/idle/intel_idle.c
+++ b/drivers/idle/intel_idle.c
@@ -557,7 +557,7 @@ static int __init intel_idle_init(void)
retval = cpuidle_register_driver(&intel_idle_driver);
if (retval) {
printk(KERN_DEBUG PREFIX "intel_idle yielding to %s",
- cpuidle_get_driver()->name);
+ cpuidle_get_driver() ? cpuidle_get_driver()->name : "none");
return retval;
}
next prev parent reply other threads:[~2012-07-31 13:40 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
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 [this message]
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=20120731134054.GD4789@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=JBeulich@suse.com \
--cc=lists+xen@internecto.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.