http://bugzilla.suse.com/show_bug.cgi?id=1011815 http://bugzilla.suse.com/show_bug.cgi?id=1011815#c31 Rodion Iafarov <riafarov@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |riafarov@suse.com --- Comment #31 from Rodion Iafarov <riafarov@suse.com> --- Hi all, so here is small update. I've performed tests by increasing loglevel to debug to get kernel messages. For 3 following cases we have same behavior: 1) console=tty 2) console=ttyX , where X = {1..9} 3) no console set during the boot kernel message is shown in active console. Even if for virtual console I set loglevel to 1 using dmesg, or disable the printing of messages to the console, I still get kernel messages on active console. For openQA we are thinking about using serial console only, I'm in progress of verifying possible side effects, as last defined console is linked as /dev/console. I believe current behavior is acceptable when is configured, as we explicitly say that we want kernel messages on tty, whereas it should not be default and possibly configurable per virtual console, so user could disable it for current console to avoid flood. Changing logging levels helps in most of the cases, whereas there is no guarantee that there is no flood of messages with KERN_CRIT level. As an more recent example of such issue: http://gershwin.arch.suse.de/tests/27#step/yast2_tftp/20 Note: there loglevel is set to debug. -- You are receiving this mail because: You are on the CC list for the bug.