From: Mark van Dijk <lists+xen@internecto.net>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Jan Beulich <JBeulich@suse.com>, xen-devel@lists.xen.org
Subject: Re: Kernel crash with acpi_processor, cpu_idle and intel_idle =y
Date: Sat, 28 Jul 2012 14:55:15 +0200 [thread overview]
Message-ID: <20120728145515.50bf4d45@internecto.net> (raw)
In-Reply-To: <20120726145535.GA5743@phenom.dumpdata.com>
> > > 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
Note: this crash only occurs with Xen, not when I boot it natively.
Does it tell you anything, or should I find a way to grab more output?
I can login via SSH to the IPMI console but unfortunately it emulates a
small screen, if you know how I can get it to not do that and just use
my current width/height I'm happy to hear it.
The relevant kernel config file is here:
http://pastebin.com/G4hR9rB9
Then, in response to your previous message Konrad about
CONFIG_ACPI_PROCESSOR_AGGREGATOR, note that this is not set.
> If you unset that ("# CONFIG_ACPI_PROCESSOR_AGGREGATOR is not set")
> that should allow MWAIT and lower states to be reached by the
> hypervisor.
I am not sure where MWAIT is, lower than C3 I suppose. In any case, the
output of the xenpm commands in my first email of this topic are on a
kernel without CONFIG_ACPI_PROCESSOR_AGGREGATOR.
So on a working kernel (i.e. without intel_idle), here is the output of
xl dmesg when booted with 'cpufreq=verbose':
http://pastebin.com/WuaLVFLG
Here is the output of 'dmesg' on Linux:
http://pastebin.com/kq1qVWv5
Stay in touch,
Mark
next prev parent reply other threads:[~2012-07-28 12:55 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 [this message]
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=20120728145515.50bf4d45@internecto.net \
--to=lists+xen@internecto.net \
--cc=JBeulich@suse.com \
--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 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.