|Summary:||kernel oops with latencytop|
Description akwatts 2011-06-16 14:28:27 UTC
Comment 1 Steven Rostedt 2011-06-16 15:36:05 UTC
It's not an oops, it's a WARN_ONCE(fmt) and I'm disappointed that WARN_ONCE does not include the text of fmt within the 'cut here'. If you go to trace.c:2725 you will see: /* Only need to warn if this is used to change the state */ WARN_ONCE(1, "tracing_enabled is deprecated. Use tracing_on"); Why is latency_top monkeying around with ftrace stuff anyway? It is suppose to be using perf syscalls. "tracing_enabled" will go away completely in the future. Don't use it.
Comment 2 akwatts 2011-06-21 02:29:09 UTC
Many thanks for taking the time to clarify this for me (I should have looked at things more closely). I agree entirely with you, though, that having the fmt text inside the cut-here block would be quite helpful. Is there any value in keeping this report open so others can react to or address the points you make?
Comment 3 Florian Mickler 2011-06-27 21:03:12 UTC
There was at one point a patch somewhere which changed the ----- cut here ---- marker into ------ trace begin, please include the message above ---- or something like that... but i think it wasn't merged as to not break tools parsing this stuff... :|