* Vince Weaver <[email protected]> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
