Messages in this thread | | | Date | Fri, 30 Jul 2021 13:00:48 +0200 | From | Petr Mladek <> | Subject | Re: [PATCH v2 2/2] printk: Add printk.console_verbose boot parameter |
| |
On Tue 2021-07-13 02:15:11, Dmitry Safonov wrote: > console_verbose() increases console loglevel to CONSOLE_LOGLEVEL_MOTORMOUTH, > which provides more information to debug a panic/oops. > > Unfortunately, in Arista we maintain some DUTs (Device Under Test) that > are configured to have 9600 baud rate. While verbose console messages > have their value to post-analyze crashes, on such setup they: > - may prevent panic/oops messages being printed > - take too long to flush on console resulting in watchdog reboot > > In all our setups we use kdump which saves dmesg buffer after panic, > so in reality those extra messages on console provide no additional value, > but rather add risk of not getting to __crash_kexec(). > > Provide printk.console_verbose boot parameter, which allows to switch off > printk being verbose on oops/panic/lockdep (making it boot parameter > instead of compile-option suggested-by Petr). > > Cc: Andrew Morton <akpm@linux-foundation.org> > Cc: John Ogness <john.ogness@linutronix.de> > Cc: Petr Mladek <pmladek@suse.com> > Cc: Sergey Senozhatsky <senozhatsky@chromium.org> > Cc: Steven Rostedt <rostedt@goodmis.org> > Signed-off-by: Dmitry Safonov <dima@arista.com>
Reviewed-by: Petr Mladek <pmladek@suse.com> Tested-by: Petr Mladek <pmladek@suse.com>
Best Regards, Petr
| |