Re: [RFC PATCH v4 9/9] printk: use a new ringbuffer implementation

Sergey Senozhatsky
2019-09-10T03:22:53Z

On (08/10/19 07:53), Thomas Gleixner wrote:
>
> Right now we have an implementation for serial only, but that already is
> useful. I nicely got (minimaly garbled) crash dumps out of an NMI
> handler. With the current mainline console code the machine just hung.
>

Thomas, any chance you can post backtraces? Just curious where exactly
current printk() and console_drivers() hung.

-ss