diff options
| author |   Patrick Ohly <patrick.ohly@intel.com> | 2015-09-18 13:49:22 +0200 |
|---|---|---|
| committer |   Richard Purdie <richard.purdie@linuxfoundation.org> | 2015-09-21 15:39:32 +0100 |
| commit | 71d7803e5b13e26fd8001e87cfbac68114ddaa30 (patch) | |
| tree | 6120eb2cfafcb21ae631b2513d53e20b3151dcd5 /meta | |
| parent | 2a4335eae4b31ea9451a665dad2ba33ae4967670 (diff) | |
| download | openembedded-core-contrib-71d7803e5b13e26fd8001e87cfbac68114ddaa30.tar.gz | |
initramfs-framework: better error reporting for invalid root boot parameter
When the "boot" parameter refers to a non-existent device, the only
visible output at normal log levels was a rather confusing:
ERROR: There's no '/dev' on rootfs.
That's because the actual error, not being able to find the root
device, was only a debug message, which gets ignored in the default
mode.
Promoting the "root '$bootparam_root' doesn't exist." message from
"debug" to "msg" gives sufficient context to understand the error. A
more intrusive change would be to change also the control flow.
Signed-off-by: Patrick Ohly <patrick.ohly@intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Diffstat (limited to 'meta')
| -rwxr-xr-x | meta/recipes-core/initrdscripts/initramfs-framework/finish | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/meta/recipes-core/initrdscripts/initramfs-framework/finish b/meta/recipes-core/initrdscripts/initramfs-framework/finish index e712ff03c6..d09bbb8bed 100755 --- a/meta/recipes-core/initrdscripts/initramfs-framework/finish +++ b/meta/recipes-core/initrdscripts/initramfs-framework/finish @@ -37,7 +37,7 @@ finish_run() { fi mount $flags $bootparam_root $ROOTFS_DIR else - debug "root '$bootparam_root' doesn't exist." + msg "root '$bootparam_root' doesn't exist." fi fi |