init: raise log level
PATCH 1/1 init: raise log level
If the kernel was booted with the "quiet" boot option we have currently no chance to see why an initrd failes.
Change KERN_WARNING to KERN_ERR to see what is going on.
Signed-off-by Richard Weinberger <[email protected]>
--- init/main.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
init/main.c +3 -3
@@ -832,7 +832,7 @@ static int __ref kernel_init(void *unused)if (ramdisk_execute_command) {if (!run_init_process (ramdisk_execute_command))return 0 ; -printk (KERN_WARNING "Failed to execute %s\n" , +printk (KERN_ERR "Failed to execute %s\n" , ramdisk_execute_command); }
@@ -845,7 +845,7 @@ static int __ref kernel_init(void *unused)if (execute_command) {if (!run_init_process (execute_command))return 0 ; -printk (KERN_WARNING "Failed to execute %s. Attempting " +printk (KERN_ERR "Failed to execute %s. Attempting " "defaults...\n" , execute_command); } if (!run_init_process("/sbin/init") ||
@@ -891,7 +891,7 @@ static noinline void __init kernel_init_freeable(void)/* Open the /dev/console on the rootfs, this should never fail */ if (sys_open ((const char __user *)"/dev/console" ,O_RDWR ,0 ) <0 ) -printk (KERN_WARNING "Warning: unable to open an initial console.\n" ); +printk (KERN_ERR "Warning: unable to open an initial console.\n" ); (void )sys_dup (0 ); (void )sys_dup (0 );
Signature · 1 line
1.8.1.4