linux-toradex.git/kernel/printk.c, branch imx-android-r13.2

Merge commit 'v3.0.8' into android-3.0

2011-10-27T22:01:19+00:00

kernel/printk: do not turn off bootconsole in printk_late_init() if keep_bootcon

2011-10-03T18:39:46+00:00

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 
Cc: David S. Miller 
Cc: Alan Cox 
Cc: Greg KH 
Acked-by: Fabio M. Di Nitto 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds 
Signed-off-by: Greg Kroah-Hartman

printk: do not handle non-sleepable notification in console_cpu_notify

2011-06-14T16:10:07+00:00

- CPU_DYING should not be handled in sleepable context

Signed-off-by: Minho Ban

kernel: printk: Add non exported function for clearing the log ring buffer

2011-06-14T16:09:18+00:00

Signed-off-by: San Mehat

printk: Fix log_buf_copy termination.

2011-06-14T16:09:14+00:00

If idx was non-zero and the log had wrapped, len did not get truncated
to stop at the last byte written to the log.

Revert "printk: remove unused code from kernel/printk.c"

2011-06-14T16:09:14+00:00

This reverts commit acff181d3574244e651913df77332e897b88bff4.

ARM: Make low-level printk work

2011-06-14T16:08:38+00:00

Makes low-level printk work.

Signed-off-by: Tony Lindgren

printk: allocate kernel log buffer earlier

2011-05-25T15:39:48+00:00

On larger systems, because of the numerous ACPI, Bootmem and EFI messages,
the static log buffer overflows before the larger one specified by the
log_buf_len param is allocated.  Minimize the overflow by allocating the
new log buffer as soon as possible.

On kernels without memblock, a later call to setup_log_buf from
kernel/init.c is the fallback.

[akpm@linux-foundation.org: coding-style fixes]
[akpm@linux-foundation.org: fix CONFIG_PRINTK=n build]
Signed-off-by: Mike Travis 
Cc: Yinghai Lu 
Cc: "H. Peter Anvin" 
Cc: Jack Steiner 
Cc: Thomas Gleixner 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

printk: allow setting DEFAULT_MESSAGE_LEVEL via Kconfig

2011-03-23T00:44:13+00:00

We've been burned by regressions/bugs which we later realized could have
been triaged quicker if only we'd paid closer attention to dmesg.  To make
it easier to audit dmesg, we'd like to make DEFAULT_MESSAGE_LEVEL
Kconfig-settable.  That way we can set it to KERN_NOTICE and audit any
messages <= KERN_WARNING.

Signed-off-by: Mandeep Singh Baines 
Cc: Ingo Molnar 
Cc: Joe Perches 
Cc: Olof Johansson 
Cc: Randy Dunlap 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

console: prevent registered consoles from dumping old kernel message over again

2011-03-23T00:44:12+00:00

For a platform with many consoles like:
 "console=tty1 console=ttyMFD2 console=ttyS0 earlyprintk=mrst"

Each time when the non "selected_console" (tty1 and ttyMFD2 here) get
registered, the existing kernel message will be printed out on registered
consoles again, the "mrst" early console will get some same message for 3
times, and "tty1" will get some for twice.

As suggested by Andrew Morton, every time a new console is registered, it
will be set as the "exclusive" console which will dump the already
existing kernel messages.

Signed-off-by: Feng Tang 
Cc: Greg KH 
Cc: Alan Cox 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds