Re: [PATCH 0/5] [GIT PULL] updates for tip/tracing/ftrace

[Ingo Molnar]

* Ingo Molnar <mingo@xxxxxxx> wrote:

> found another, unrelated lockup with the event tracer:
> 
> europe:/debug/tracing/events/sched/sched_wakeup_new> cat enable 
> 0
> europe:/debug/tracing/events/sched/sched_wakeup_new> echo 1 > enable
> europe:/debug/tracing/events/sched/sched_wakeup_new> sync
> europe:/debug/tracing/events/sched/sched_wakeup_new> cat 
> ../../../trace_pipe 
>            <...>-2870  [000]   688.730160: sched_wakeup_new: task 
> bash:2898 [120] success=1
>            <...>-2870  [001]   689.945375: sched_wakeup_new: task 
> bash:2899 [120] success=1
> 
> [hard lockup]

ok, tracked it down - it's the new trace_wake_up() from within 
wake_up_new_task() => bad idea.

I think this was introduced via:

6eaaa5d: tracing/core: use appropriate waiting on trace_pipe

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/