[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <52946261.8020408@hitachi.com>
Date: Tue, 26 Nov 2013 17:57:05 +0900
From: Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>
To: Jovi Zhangwei <jovi.zhangwei@...il.com>
Cc: Steven Rostedt <rostedt@...dmis.org>,
Oleg Nesterov <oleg@...hat.com>,
LKML <linux-kernel@...r.kernel.org>,
"yrl.pp-manager.tt@...achi.com" <yrl.pp-manager.tt@...achi.com>
Subject: Re: [BUG] 3.13-rc1 kernel crash when enable all tracepoints
(2013/11/26 16:20), Jovi Zhangwei wrote:
> I'm not sure this relate with ftrace:function event, from the
> crash log, it seems more like caused by lock events.
>
> Now I only enable lock events (lockdep compiled in my box), below
> two commands both can crash system.
That is not the lockdep, but the lockstat. :)
>
> #echo 1 > /sys/kernel/debug/tracing/events/lock/lock_acquire/enable
> or.
> #echo 1 > /sys/kernel/debug/tracing/events/lock/lock_release/enable
>
> According to the log, it seems like a recursion tracing bug.
>
> register lock event -> jump_label_update -> text_poke_bp ->
> on_each_cpu -> local_apic_timer_interrupt -> ktime_get_update_offsets
> -> lock_release
OK, the problem is in the lock_acquire/release events.
> (Perhaps the crash you reproduced is another crash? similar crash log?)
Right, that was my mistake. Now I got same error log on kvm too.
This should be fixed.
Thank you,
--
Masami HIRAMATSU
IT Management Research Dept. Linux Technology Center
Hitachi, Ltd., Yokohama Research Laboratory
E-mail: masami.hiramatsu.pt@...achi.com
--
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