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 for Android: free password hash cracker in your pocket

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

Message-Id: <201101311114.11935.rjw@sisk.pl>
Date:	Mon, 31 Jan 2011 11:14:11 +0100
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Ozan Çağlayan <ozan@...dus.org.tr>
Cc:	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, Ozan Çağlayan wrote:
> On 31.01.2011 11:50, Rafael J. Wysocki wrote:
> > On Monday, January 31, 2011, Ozan Çağlayan wrote:
> >> On 31.01.2011 00:48, Rafael J. Wysocki wrote:
> >>
> >>> Does booting with "nolapic" help on all of the affected systems?
> >>>
> >>> Also, does disabling the CPUidle during boot help?
> >>>
> >>> Finally, is the problem reproducible with CONFIG_NO_HZ unset?
> >>
> >> Well on two machines, nolapic cures the boot hang and on one machine it
> >> cures the random shutdown hangs.
> >>
> >> 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.
> 
> Okay but on Asus X61S idle fallbacks to cpuidle:
> 
> intel_idle: MWAIT substates: 0x3122220
> intel_idle: does not run on family 6 model 23
> 
> so forcing max_cstate to 0 will turn off the cpuidle on those machines too?

In those cases you can use processor.max_cstate=0 I think.

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/