[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150714192624.GO3717@linux.vnet.ibm.com>
Date: Tue, 14 Jul 2015 12:26:24 -0700
From: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To: Fabio Estevam <festevam@...il.com>
Cc: Russell King <linux@....linux.org.uk>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
Peter Zijlstra <peterz@...radead.org>, rostedt@...dmis.org,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: mx6: suspicious RCU usage
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@...il.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
--
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