linux-kernel - Re: Common boot/shutdown issues with the latest 2.6.37 (Mostly Asus laptops)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <201101311924.33098.rjw@sisk.pl>
Date:	Mon, 31 Jan 2011 19:24:32 +0100
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Richard Schütz <r.schtz@...nline.de>
Cc:	Ozan Çağlayan <ozan@...dus.org.tr>,
	Lionel Debroux <lionel_debroux@...oo.fr>,
	linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org,
	platform-driver-x86@...r.kernel.org, colin.king@...onical.com
Subject: Re: Common boot/shutdown issues with the latest 2.6.37 (Mostly Asus laptops)

On Monday, January 31, 2011, Richard Schütz 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=0 should do the trick.
> >>
> >> intel_idle.max_cstate=0 causes a fallback to the acpi_idle driver. So it
> >> does not disable the C-states directly.
> >
> > What about not building the acpi_idle driver, then?
> 
> 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-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/