linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shawn Guo <shawn.guo@linaro.org>
To: Subodh Nijsure <snijsure@grid-net.com>
Cc: paulmck@linux.vnet.ibm.com, linux-mtd@lists.infradead.org,
	Linux Kernel Maling List <linux-kernel@vger.kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	Artem Bityutskiy <dedekind1@gmail.com>
Subject: Re: RCU warning during UBI file system mount
Date: Wed, 5 Sep 2012 11:51:10 +0800	[thread overview]
Message-ID: <20120905035108.GV2362@S2101-09.ap.freescale.net> (raw)
In-Reply-To: <50462190.7090702@grid-net.com>

On Tue, Sep 04, 2012 at 08:43:12AM -0700, Subodh Nijsure wrote:
> MX28 is ARM device. I removed following from my config and these
> warnings went away.
> 
> CONFIG_CPU_IDLE=y
> CONFIG_CPU_IDLE_GOV_LADDER=y
> CONFIG_CPU_IDLE_GOV_MENU=y
> 
There is no cpuidle implemented on imx28.  I do not understand how
these options influence the result here.

> I have attached the kernel configuration file I used.
> 
> It doesn't affect specific hw I am working with as device is not
> required to enter idle mode.
> I am Cc-ing linux-arm folks,  in case someone on arm platform
> requires CPU idele &, RCU to work.
> 
I just ran a case with CONFIG_CPU_IDLE and RCU support and failed
to reproduce the warning.  Is this something specific to gpmi-nand
or we can see it with any other imx28 drivers/cases?  Sorry, I do
not have NAND flash set up on my imx28 board.

-- 
Regards,
Shawn

      parent reply	other threads:[~2012-09-05  3:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5042EC5D.1010207@grid-net.com>
2012-09-04  7:46 ` Artem Bityutskiy
2012-09-04 14:48   ` Paul E. McKenney
2012-09-04 15:43     ` Subodh Nijsure
2012-09-04 19:54       ` Paul E. McKenney
2012-09-05  3:51       ` Shawn Guo [this message]

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=20120905035108.GV2362@S2101-09.ap.freescale.net \
    --to=shawn.guo@linaro.org \
    --cc=dedekind1@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=snijsure@grid-net.com \
    --subject='Re: RCU warning during UBI file system mount' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).