From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Mark van Dijk <lists+xen@internecto.net>
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: Tue, 31 Jul 2012 19:42:07 -0400 [thread overview]
Message-ID: <20120731234207.GJ32698@phenom.dumpdata.com> (raw)
In-Reply-To: <20120731235039.6cddfc55@internecto.net>
On Tue, Jul 31, 2012 at 11:50:39PM +0200, Mark van Dijk wrote:
> Message 20120731134054.GD4789@phenom.dumpdata.com contained:
>
> >Duh! That is easy enough to fix. Mark, can you please try testing with
> >this patch (and obviously enable the CONFIG_INTEL_IDLE)
> >(patch omitted)
>
> Sure, I'll try it right now.
>
> Incidentally I came across a thread suggesting that there is quite a
> lot happening in the world of cpuidle. So I want to make sure that
> any implementation from your end isn't / won't be in conflict with code
> from other sources.
>
> https://lkml.org/lkml/2012/6/28/186
> https://lkml.org/lkml/2012/6/29/48
ah yes. I recall seeing those. I ought to be OK.
>
> I trust you'll be able to track this down far better than I can,
> meanwhile I'll test this patch you sent me.
Thank you.
next prev parent reply other threads:[~2012-07-31 23:42 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
2012-07-31 21:50 ` Mark van Dijk
2012-07-31 23:42 ` Konrad Rzeszutek Wilk [this message]
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=20120731234207.GJ32698@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 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).