From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark van Dijk Subject: Re: Kernel crash with acpi_processor, cpu_idle and intel_idle =y Date: Tue, 31 Jul 2012 23:50:39 +0200 Message-ID: <20120731235039.6cddfc55@internecto.net> References: <20120722181611.7ae03506@internecto.net> <20120723142025.GB793@phenom.dumpdata.com> <20120726022527.4d3f6e4a@internecto.net> <20120726140552.GD28024@phenom.dumpdata.com> <501176DD0200007800090A32@nat28.tlf.novell.com> <20120726145535.GA5743@phenom.dumpdata.com> <20120728145515.50bf4d45@internecto.net> <501657C70200007800091357@nat28.tlf.novell.com> <20120731134054.GD4789@phenom.dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20120731134054.GD4789@phenom.dumpdata.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Konrad Rzeszutek Wilk Cc: Jan Beulich , xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org 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 I trust you'll be able to track this down far better than I can, meanwhile I'll test this patch you sent me. -- Kind regards, Mark van Dijk. ,-------------------------------- ---------------------------' Tue Jul 31 21:40 UTC 2012 Today is Boomtime, the 66th day of Confusion in the YOLD 3178