[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1267672706.10871.97.camel@gandalf.stny.rr.com>
Date: Wed, 03 Mar 2010 22:18:26 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Américo Wang <xiyou.wangcong@...il.com>
Cc: Frederic Weisbecker <fweisbec@...il.com>,
LKML <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...e.hu>,
Peter Zijlstra <peterz@...radead.org>
Subject: Re: 2.6.33: ftrace triggers soft lockup
On Thu, 2010-03-04 at 11:01 +0800, Américo Wang wrote:
> >
> > So it is stuck in stop machine. I wonder where exactly. I see some do_exit
> > at the top but I wonder how much they are reliable.
>
> Well, I think 'kstop' is just random, sometimes I got 'watchdog' or some other
> process.
>
> >
> > Anyway, as Steve said, we really need a full config to reproduce it.
> >
>
> Done in another reply.
Thanks!
Frederic, I notice that lockdep is on, did anything change that might
slow down the code in lockdep, or is the function graph tracer doing
more locking?
I'm betting that we are hitting a live lock. That is, an interrupt goes
off, it is being traced, and the function graph is tracing it, but some
locking is happening (although it also tracks disabling of interrupts)
and this slows the interrupt handler down enough that when it finishes,
another interrupt goes off.
Américo,
Could you disable LOCKDEP and see if you still encounter this lockup?
Thanks,
-- Steve
--
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