aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPavel Tatashin <[email protected]>2019-12-04 10:59:14 -0500
committerWill Deacon <[email protected]>2020-01-08 16:32:55 +0000
commitd42cc530b18db2dd9de621238d33670841aabc36 (patch)
treed60c45b52494133d2e4ca04fabab03fff2f55fdf
parent46cf053efec6a3a5f343fead837777efe8252a46 (diff)
kexec: quiet down kexec reboot
Here is a regular kexec command sequence and output: ===== $ kexec --reuse-cmdline -i --load Image $ kexec -e [ 161.342002] kexec_core: Starting new kernel Welcome to Buildroot buildroot login: ===== Even when "quiet" kernel parameter is specified, "kexec_core: Starting new kernel" is printed. This message has KERN_EMERG level, but there is no emergency, it is a normal kexec operation, so quiet it down to appropriate KERN_NOTICE. Machines that have slow console baud rate benefit from less output. Signed-off-by: Pavel Tatashin <[email protected]> Reviewed-by: Simon Horman <[email protected]> Acked-by: Dave Young <[email protected]> Signed-off-by: Will Deacon <[email protected]>
-rw-r--r--kernel/kexec_core.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/kernel/kexec_core.c b/kernel/kexec_core.c
index 15d70a90b50d..f7ae04b8de6f 100644
--- a/kernel/kexec_core.c
+++ b/kernel/kexec_core.c
@@ -1171,7 +1171,7 @@ int kernel_kexec(void)
* CPU hotplug again; so re-enable it here.
*/
cpu_hotplug_enable();
- pr_emerg("Starting new kernel\n");
+ pr_notice("Starting new kernel\n");
machine_shutdown();
}