Messages in this thread | | | Date | Sat, 26 Oct 2013 10:48:36 +0200 | From | Ingo Molnar <> | Subject | Re: perf/ftrace lockup on 3.12-rc6 with trigger code |
| |
* Vince Weaver <vincent.weaver@maine.edu> wrote:
> I don't know if there are any better ways to try to debug things > than the printk route. Though that has its own problems as the > printk's themselves start showing up in the ftrace traces.
One additional brute-force method is earlyprintk=...,keep and marking the (handful of) earlyprintk functions (and snprintf) notrace, plus turning off printk itself completely.
That gives a completely instrumentation-free and locking-free console output function of last resort :-/
Thanks,
Ingo
| |