[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180430180011.2ded931c@gandalf.local.home>
Date: Mon, 30 Apr 2018 18:00:11 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Joel Fernandes <joelaf@...gle.com>
Cc: LKML <linux-kernel@...r.kernel.org>,
Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...hat.com>,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
Tom Zanussi <tom.zanussi@...ux.intel.com>,
Namhyung Kim <namhyung@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Boqun Feng <boqun.feng@...il.com>,
Paul McKenney <paulmck@...ux.vnet.ibm.com>,
"Cc: Frederic Weisbecker" <fweisbec@...il.com>,
Randy Dunlap <rdunlap@...radead.org>,
Masami Hiramatsu <mhiramat@...nel.org>,
Fenguang Wu <fengguang.wu@...el.com>,
Baohong Liu <baohong.liu@...el.com>,
Vedang Patel <vedang.patel@...el.com>,
"Cc: Android Kernel" <kernel-team@...roid.com>
Subject: Re: [PATCH] softirq: reorder trace_softirqs_on to prevent lockdep
splat
On Mon, 30 Apr 2018 17:01:04 +0000
Joel Fernandes <joelaf@...gle.com> wrote:
Tried 4.17-rc3 and see it too. Could be difference in configs? Also, the
> environment is a Qemu system with single CPU 1GB memory. Attached is the
> config.
>
> I think when I had multiple CPUs it was harder to trigger it, but can't
> really remember now. There was a time when triggering it was quite
> intermittent.
>
Bah, I didn't have CONFIG_DEBUG_LOCKDEP enabled, and that is what does
the backtrace.
-- Steve
Powered by blists - more mailing lists