diff options
| author | Nishanth Aravamudan <nacc@us.ibm.com> | 2011-08-25 15:59:11 -0700 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@suse.de> | 2011-10-03 11:39:46 -0700 |
| commit | 7f4e15693062aa1afcfc8f05f6790baf29bacfa3 (patch) | |
| tree | d4ef5496034aaaeba1ce945f810ee56ec2a5fce5 /arch/powerpc/sysdev/fsl_rio.c | |
| parent | 04aa37b5f943920017ad094e776cd5514b1a9246 (diff) | |
| download | kernel_samsung_smdk4412-7f4e15693062aa1afcfc8f05f6790baf29bacfa3.zip kernel_samsung_smdk4412-7f4e15693062aa1afcfc8f05f6790baf29bacfa3.tar.gz kernel_samsung_smdk4412-7f4e15693062aa1afcfc8f05f6790baf29bacfa3.tar.bz2 | |
kernel/printk: do not turn off bootconsole in printk_late_init() if keep_bootcon
commit 4c30c6f566c0989ddaee3407da44751e340a63ed upstream.
It seems that 7bf693951a8e ("console: allow to retain boot console via
boot option keep_bootcon") doesn't always achieve what it aims, as when
printk_late_init() runs it unconditionally turns off all boot consoles.
With this patch, I am able to see more messages on the boot console in
KVM guests than I can without, when keep_bootcon is specified.
I think it is appropriate for the relevant -stable trees. However, it's
more of an annoyance than a serious bug (ideally you don't need to keep
the boot console around as console handover should be working -- I was
encountering a situation where the console handover wasn't working and
not having the boot console available meant I couldn't see why).
Signed-off-by: Nishanth Aravamudan <nacc@us.ibm.com>
Cc: David S. Miller <davem@davemloft.net>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Greg KH <gregkh@suse.de>
Acked-by: Fabio M. Di Nitto <fdinitto@redhat.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'arch/powerpc/sysdev/fsl_rio.c')
0 files changed, 0 insertions, 0 deletions