[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20120206070442.GD5941@linux.vnet.ibm.com>
Date: Sun, 5 Feb 2012 23:04:42 -0800
From: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To: Kevin Hilman <khilman@...com>
Cc: linux-kernel@...r.kernel.org, mingo@...e.hu, laijs@...fujitsu.com,
dipankar@...ibm.com, akpm@...ux-foundation.org,
mathieu.desnoyers@...ymtl.ca, josh@...htriplett.org,
niv@...ibm.com, tglx@...utronix.de, peterz@...radead.org,
rostedt@...dmis.org, Valdis.Kletnieks@...edu, dhowells@...hat.com,
eric.dumazet@...il.com, darren@...art.com, fweisbec@...il.com,
patches@...aro.org
Subject: Re: [PATCH RFC 0/41] RCU commits for 3.4
On Fri, Feb 03, 2012 at 11:54:40AM -0800, Kevin Hilman wrote:
> "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com> writes:
>
> > On Thu, Feb 02, 2012 at 02:47:14PM -0800, Kevin Hilman wrote:
> >> Hi Paul,
> >>
> >> "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com> writes:
> >>
> >> > This patchset makes RCU more aggressive about entering dyntick-idle mode
> >> > in order to improve energy efficiency,
> >>
> >> I gave this series a spin on an ARM/SMP platform (OMAP4) and the boot
> >> hung (tail end of boot log below.) I then realized that had isolcpus=1
> >> on the cmdline from a previous experiment. Removing isolcpus from the
> >> cmdline got me back to a working boot.
> >>
> >> IIRC, some want to remove isolcpus, so I'm not sure if it's expected to
> >> work with your series, but thought you'd want to know.
> >
> > Not expected behavior, thank you for testing!
> >
> > Could you please share your .config?
>
> Sure, attached.
Interesting...
Could you please try to reproduce with CONFIG_RCU_CPU_STALL_INFO=y?
That will give me some additional diagnostic information.
Thanx, Paul
--
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/
Powered by blists - more mailing lists