linux-kernel - Re: next-20120313 cpuidle freezes when booting

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]

Date:	Wed, 14 Mar 2012 13:30:57 -0700 (PDT)
From:	Hugh Dickins <hughd@...gle.com>
To:	Daniel Lezcano <daniel.lezcano@...aro.org>
cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Robert Lee <rob.lee@...aro.org>, Jean Pihet <j-pihet@...com>,
	Kevin Hilman <khilman@...com>,
	Deepthi Dharwar <deepthi@...ux.vnet.ibm.com>,
	Dan Carpenter <dan.carpenter@...cle.com>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: next-20120313 cpuidle freezes when booting

On Wed, 14 Mar 2012, Daniel Lezcano wrote:
> On 03/14/2012 08:03 PM, Hugh Dickins wrote:
> > On Wed, 14 Mar 2012, Daniel Lezcano wrote:
> > > On 03/13/2012 11:29 PM, Hugh Dickins wrote:
> > > > 
> > > > Yesterday's 3.3.0-rc7-next-20120313 gives me unpredictable freezes
> > > > on x86_64, on a ThinkPad T420s - I've not dared it on more machines.
> > > 
> > > is it possible you give the cpuidle driver your host is using ?
> > 
> > "grep IDLE .config" tells me:
> > 
> > CONFIG_ARCH_HAS_CPU_IDLE_WAIT=y
> > CONFIG_ARCH_HAS_DEFAULT_IDLE=y
> > CONFIG_CPU_IDLE=y
> > CONFIG_CPU_IDLE_GOV_LADDER=y
> > CONFIG_CPU_IDLE_GOV_MENU=y
> > CONFIG_INTEL_IDLE=y
> > # CONFIG_I7300_IDLE is not set
> > 
> > but I've a feeling that isn't what you need to know.
> 
> Thanks for these informations, I forgot to ask you for them.
> By the way, do you have CONFIG_ARCH_HAS_CPU_RELAX  ?

Yes.

> 
> > Is there some /proc or /sys file I can read to tell you?
> 
> Yes, the content of /sys/devices/system/cpu/cpuidle/current_driver

intel_idle

> and /sys/devices/system/cpu/cpuidle/current_governor_ro

menu

> 
> > Though if it's something that changes dynamically, then what
> > I read now might not be what it would say when things go wrong.
> 
> No, that won't change, so the information should be enough for me to find the
> code path where the regression is.
> 
> > I expect you've realized by now, I haven't a clue about cpuidle
> > drivers: I hadn't even realized that idleness needs a driver.
> 
> No problem, thanks for git bisecting and find the culprit :)

Thank you - let me know if you've something you'd like me to try.

Hugh
--
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/