From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Rafael J. Wysocki" Subject: Re: Common boot/shutdown issues with the latest 2.6.37 (Mostly Asus laptops) Date: Mon, 31 Jan 2011 19:24:32 +0100 Message-ID: <201101311924.33098.rjw@sisk.pl> References: <556624.21214.qm@web28409.mail.ukl.yahoo.com> <201101311123.14704.rjw@sisk.pl> <4D468F1F.8030704@t-online.de> Mime-Version: 1.0 Content-Type: Text/Plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-Reply-To: <4D468F1F.8030704@t-online.de> Sender: linux-acpi-owner@vger.kernel.org To: Richard =?utf-8?q?Sch=C3=BCtz?= Cc: Ozan =?utf-8?q?=C3=87a=C4=9Flayan?= , Lionel Debroux , linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org, platform-driver-x86@vger.kernel.org, colin.king@canonical.com List-Id: platform-driver-x86.vger.kernel.org On Monday, January 31, 2011, Richard Sch=C3=BCtz wrote: > >>>> I'll compile a kernel with CONFIG_NO_HZ to see what happens but = how do I > >>>> disable cpuidle during boot? I've checked the kernel-parameters.= txt but > >>>> there's no cpuidle related boot parameter there. > >>> > >>> Booting with intel_idle.max_cstate=3D0 should do the trick. > >> > >> intel_idle.max_cstate=3D0 causes a fallback to the acpi_idle drive= r. So it > >> does not disable the C-states directly. > > > > What about not building the acpi_idle driver, then? >=20 > Or just use the processor.max_cstate parameter then. As I wrote a couple of messages ago, https://lkml.org/lkml/2011/1/31/52= . Sure, that should do the trick too. Thanks, Rafael -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" i= n the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html