From: Hugh Dickins <hughd@google•com>
To: Daniel Lezcano <daniel.lezcano@linaro•org>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
Andrew Morton <akpm@linux-foundation•org>,
Robert Lee <rob.lee@linaro•org>, Jean Pihet <j-pihet@ti•com>,
Kevin Hilman <khilman@ti•com>,
Deepthi Dharwar <deepthi@linux•vnet.ibm.com>,
Dan Carpenter <dan.carpenter@oracle•com>,
linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: Re: next-20120313 cpuidle freezes when booting
Date: Wed, 14 Mar 2012 12:03:37 -0700 (PDT) [thread overview]
Message-ID: <alpine.LSU.2.00.1203141156490.3826@eggly.anvils> (raw)
In-Reply-To: <4F608116.80508@linaro.org>
On Wed, 14 Mar 2012, Daniel Lezcano wrote:
> On 03/13/2012 11:29 PM, Hugh Dickins wrote:
> > Hi Stephen,
> >
> > 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.
> >
> > Usually when booting up (sometimes just after Freeing unused kernel
> > memory, sometimes random places elsewhere), but occasionally it manages
> > to get as far as X; doesn't usually manage to complete suspend+resume.
> >
> > 3.3.0-rc6-nex-20120309 behaved similarly; the last I tried before
> > that was 3.3.0-rc5-next20120227, which was okay.
> >
> > Bisection led me to "cpuidle: Add common time keeping and irq enabling",
> > (from the cpuidle-cons tree I think), and reverting that has so far
> > given me a working system (it's a success if I complete this mail).
> >
> > Below is the patch I've used to revert it (for other people having
> > problems with recent linux-next to try); but it's not quite correct,
> > because you did a merge on conflicting trees there, and I didn't spend
> > time to unravel all that, just get a working x86 system - since I've
> > left out some of your merge (in arch/arm/kernel/Makefile and arch/arm/
> > mach-at91/cpuidle.c), this reversion probably breaks arm as is.
>
> Hi Hugh,
>
> 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.
Is there some /proc or /sys file I can read to tell you?
Though if it's something that changes dynamically, then what
I read now might not be what it would say when things go wrong.
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.
Hugh
next prev parent reply other threads:[~2012-03-14 19:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-13 22:29 next-20120313 cpuidle freezes when booting Hugh Dickins
2012-03-14 11:29 ` Daniel Lezcano
2012-03-14 19:03 ` Hugh Dickins [this message]
2012-03-14 19:46 ` Daniel Lezcano
2012-03-14 20:30 ` Hugh Dickins
2012-03-15 0:09 ` [PATCH] cpuidle : fix random hangs with intel_idle Daniel Lezcano
2012-03-15 0:14 ` Stephen Rothwell
2012-03-15 0:23 ` Hugh Dickins
2012-03-15 2:58 ` Stephen Rothwell
2012-03-16 13:37 ` Amit Kucheria
2012-03-16 14:26 ` Stephen Rothwell
2012-03-20 16:27 ` Rob Lee
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LSU.2.00.1203141156490.3826@eggly.anvils \
--to=hughd@google$(echo .)com \
--cc=akpm@linux-foundation$(echo .)org \
--cc=dan.carpenter@oracle$(echo .)com \
--cc=daniel.lezcano@linaro$(echo .)org \
--cc=deepthi@linux$(echo .)vnet.ibm.com \
--cc=j-pihet@ti$(echo .)com \
--cc=khilman@ti$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=rob.lee@linaro$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox