All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Hugh Dickins <hughd@google.com>
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:29:26 +0100	[thread overview]
Message-ID: <4F608116.80508@linaro.org> (raw)
In-Reply-To: <alpine.LSU.2.00.1203131454500.1335@eggly.anvils>

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 ?

Thanks
   -- Daniel

-- 
  <http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog

  reply	other threads:[~2012-03-14 11:29 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 [this message]
2012-03-14 19:03   ` Hugh Dickins
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=4F608116.80508@linaro.org \
    --to=daniel.lezcano@linaro.org \
    --cc=akpm@linux-foundation.org \
    --cc=dan.carpenter@oracle.com \
    --cc=deepthi@linux.vnet.ibm.com \
    --cc=hughd@google.com \
    --cc=j-pihet@ti.com \
    --cc=khilman@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rob.lee@linaro.org \
    --cc=sfr@canb.auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.