Messages in this thread | | | Date | Tue, 19 Jun 2018 10:08:30 +0200 | From | Peter Zijlstra <> | Subject | Re: [RFC][PATCH 0/6] Use printk_safe context for TTY and UART port locks |
| |
On Mon, Jun 18, 2018 at 02:38:18PM +0100, Alan Cox wrote: > Given printk nowdays is already somewhat unreliable with all the perf > related changes,
printk is a steaming pile of @#$#@, unreliable doesn't even begin to cover it.
> and we have other good debug tools
What other good debug tools do you have? The only thing I have that actually works is earlyser/8250_early -- and I route everything printk into that.
| |