On (12/05/18 11:50), Sergey Senozhatsky wrote:
>
> panic_print_sys_info() can be very verbose, and it happens much later
> than dump_stack() from panic CPU. So you are guaranteed to have same
> problems you are trying to avoid: "the original context gets
> lost on screen" and "confused people post bad bug reports".
>
And it probably would be _a bit_ better to do panic_print_sys_info()
before console_flush_on_panic().
---
debug_locks_off();
- console_flush_on_panic();
-
panic_print_sys_info();
+ console_flush_on_panic();
---
-ss
