Bug 9354

Summary: pTest image does not boot after install
Product: [Build System, Metadata & Runtime] BSPs Reporter: Cristina Agurida <cristina-danielax.agurida>
Component: bsps-runtimeAssignee: Robert Yang <liezhi.yang>
Status: RESOLVED FIXED QA Contact: Francisco Pedraza <francisco.j.pedraza.gonzalez>
Severity: normal    
Priority: High CC: alexandru.c.georgescu, california.l.sullivan, costin.c.constantin, francisco.j.pedraza.gonzalez, yp.kernel.watcher, yp.watcher
Version: 2.1   
Target Milestone: 2.1 M4   
Hardware: NUC   
OS: x86_64   
Whiteboard:
OS type for building Yocto: --- Type of Regression: Regression (Used to work)
Verified: Documentation change: No (bug/feature does not impact docs)
Attachments:
Description Flags
error message
none
Miinow Max none

Description Cristina Agurida 2016-03-30 12:50:20 UTC 
Created attachment 3071 [details]
error message

BUILD: 2.1_M3.rc2: 21823cb466e79540567ad1a43ae6f93d850e4057
ENVIRONMENT: genericx86-64
HARDWARE: NUC (model: NUC5i5RYH)
IMAGE: core-image-sato-sdk

STEPS TO REPRODUCE: 
1. Download image from autobuilder: http://autobuilder.yoctoproject.org/pub/releases/yocto-2.1_M3.rc2/machines/genericx86-64/core-image-sato-sdk-ptest-genericx86-64.hddimg

2. Install the image on NUC using an USB stick.

3. Try to boot the image.

EXPECTED OUTCOME: 
Image should boot successfully.

ACTUAL OUTCOME:

After install, when trying to boot, the message "kernel panic - not syncing: invalid configuration from end user prevents continuing" appears on screen. 
I tried also with a built local image and it throws the same error.
See attached photo.
Comment 1 Bruce Ashfield 2016-03-30 16:31:54 UTC 
Saul: any ideas on this ?
Comment 2 Francisco Pedraza 2016-03-30 21:24:42 UTC 
This issue is also reproducible on 
NUC - Image Genericx86-64
link: http://autobuilder.yoctoproject.org/pub/releases/yocto-2.1_M3.rc2/machines/genericx86-64/core-image-sato-sdk-genericx86-64.hddimg

NUC models: NUC6i5SYH and D54250WYK.
Comment 3 Alexandru Georgescu 2016-03-31 08:36:19 UTC 
We could build locally and reproduce the issue as well.
Comment 4 California Sullivan 2016-04-01 00:39:45 UTC 
Breaks on commit 4ebaeb281bc70a9962ab9f4c49c0a2587fe3487a

It appears that the APPEND_prepend = " ${ROOT} " adds an additional "root=/dev/ram0" to the kernel command line, which carries over on install and causes this kernel panic.
Comment 5 Robert Yang 2016-04-01 02:41:01 UTC 
I can't reproduce it on on qemu or my note book, maybe I will try it on a EFI device.
Comment 6 Costin 2016-04-01 13:05:29 UTC 
Hello,

Same is happening on minnow max for genericx86, genericx86-64 and genericx86_lsb.

Attached are the pictures for kernel panic screen
Comment 7 Costin 2016-04-01 13:07:07 UTC 
Created attachment 3085 [details]
Miinow Max

Minnow Max kpanic
Comment 9 California Sullivan 2016-04-04 21:18:44 UTC 
> Would you please try this patch: 

This patch fixes the kernel panic for me.