All of lore.kernel.org
 help / color / mirror / Atom feed
From: paulmck@linux.vnet.ibm.com (Paul E. McKenney)
To: linux-arm-kernel@lists.infradead.org
Subject: mx6: suspicious RCU usage
Date: Tue, 14 Jul 2015 12:26:24 -0700	[thread overview]
Message-ID: <20150714192624.GO3717@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAOMZO5C1+qQyFqfrfWatsY_yjO952gk1o9qmJJgMmjDEAix21g@mail.gmail.com>

On Tue, Jul 14, 2015 at 01:59:10PM -0300, Fabio Estevam wrote:
> On Tue, Jul 14, 2015 at 1:44 PM, Fabio Estevam <festevam@gmail.com> wrote:
> 
> > With your patch applied I am running several suspend/resume cycles and
> > I am seeing different problems now from time to time (like 1 out 10
> > times). The kernel dump does not look like the same every time, but
> > here is one example:
> 
> Here is another one I just got, and it seems to be more informative:
> 
> http://pastebin.com/T4YxuLCg

This might simply be a symptom of the earlier "Unable to handle
kernel paging request at virtual address 708ebbfa".  However, the
usual cause of the later "rcu_read_lock() used illegally while idle!"
is just that.  In this case, might the interrupt have occurred
without irq_enter() being invoked?

(But there are probably two interleaved stack traces, and I am not
certain that I am getting them untangled properly.)

							Thanx, Paul

WARNING: multiple messages have this Message-ID (diff)
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: Russell King <linux@arm.linux.org.uk>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	Peter Zijlstra <peterz@infradead.org>,
	rostedt@goodmis.org, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: mx6: suspicious RCU usage
Date: Tue, 14 Jul 2015 12:26:24 -0700	[thread overview]
Message-ID: <20150714192624.GO3717@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAOMZO5C1+qQyFqfrfWatsY_yjO952gk1o9qmJJgMmjDEAix21g@mail.gmail.com>

On Tue, Jul 14, 2015 at 01:59:10PM -0300, Fabio Estevam wrote:
> On Tue, Jul 14, 2015 at 1:44 PM, Fabio Estevam <festevam@gmail.com> wrote:
> 
> > With your patch applied I am running several suspend/resume cycles and
> > I am seeing different problems now from time to time (like 1 out 10
> > times). The kernel dump does not look like the same every time, but
> > here is one example:
> 
> Here is another one I just got, and it seems to be more informative:
> 
> http://pastebin.com/T4YxuLCg

This might simply be a symptom of the earlier "Unable to handle
kernel paging request at virtual address 708ebbfa".  However, the
usual cause of the later "rcu_read_lock() used illegally while idle!"
is just that.  In this case, might the interrupt have occurred
without irq_enter() being invoked?

(But there are probably two interleaved stack traces, and I am not
certain that I am getting them untangled properly.)

							Thanx, Paul


  reply	other threads:[~2015-07-14 19:26 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-14 15:54 mx6: suspicious RCU usage Fabio Estevam
2015-07-14 15:54 ` Fabio Estevam
2015-07-14 16:00 ` Paul E. McKenney
2015-07-14 16:00   ` Paul E. McKenney
2015-07-14 16:06   ` Fabio Estevam
2015-07-14 16:06     ` Fabio Estevam
2015-07-14 16:26     ` Paul E. McKenney
2015-07-14 16:26       ` Paul E. McKenney
2015-07-14 16:44       ` Fabio Estevam
2015-07-14 16:44         ` Fabio Estevam
2015-07-14 16:54         ` Paul E. McKenney
2015-07-14 16:54           ` Paul E. McKenney
2015-07-14 16:59         ` Fabio Estevam
2015-07-14 16:59           ` Fabio Estevam
2015-07-14 19:26           ` Paul E. McKenney [this message]
2015-07-14 19:26             ` Paul E. McKenney
2015-07-14 20:49       ` Russell King - ARM Linux
2015-07-14 20:49         ` Russell King - ARM Linux
2015-07-14 21:31         ` Paul E. McKenney
2015-07-14 21:31           ` Paul E. McKenney
2015-07-14 16:08   ` Paul E. McKenney
2015-07-14 16:08     ` Paul E. McKenney

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=20150714192624.GO3717@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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.