The yocto 10.3 kernel fails to boot on romley-ivb. Tried booting both from PXE/NFS and hddimg on USB. Due to the specifics of our test environment I cannot paste the entire log, but I will transcribe the following messages: Please append a correct "root=" boot option: here are the availalbe partitions: VFS: Unable to mount root fs on unknown-block(0,0) User confirguration error - no valid root filesystem found Kernel panic - not synching: Invalid configuration from end user prevents continuing CPU: 0 PID: 1 Comm: swapper Not tainted 3.10.32-ltsi-yocto-standard #1 And then follows the standarad kernel panic call trace... I did a bit of digging and identified the problem as being introduced by commit: 09d485dcce6ed4b654abc0c8a630f1d36bc1a7d6: linux-yocto: Remove redundant recipes Reverting this commit makes the kernel bootable again.
This suggests the common kernel recipe is missing some CONFIG_ option for your target boot device. Which device and bus are trying to boot from? Assigning to Boon Leong as it's their BSP - but I remain on Cc as that's my patch and the common kernel effort is largely on my plate. We need to sort out which configuration option is required that is getting dropped and then ensure it is enabled.
If I understand your question, I tried booting two ways: from a Sandisk Cruzer 2.1 USb flash drive using the hddimg and through the network using Intel boot agent VE 1.3.98 / PXE 2.1, kernel on tftp and rootfs on NFS.
Oh, my apologies, you mentioned that in the opening comment. Can you please share the entire boot log captured from serial using screen -L or similar? I will verify the live-boot fragment is getting built, as well as the network and NFS options. Also, could you quickly post the kernel command line from the syslinux config on the hddimg?
Created attachment 1898 [details] kernel panic message when booting the romely-ivb
Hi, Due to our setup I don't have physical access to the board and it doesn't output the entire bootlog on serial, so I can't provide a full log. If it helps, I am attaching, however, a printscreen taken with the IPMI interface with the full kernel panic message. Also here is the content of syslinux.cfg on the hddimg: # Automatically created by OE ALLOWOPTIONS 1 SERIAL 0 115200 DEFAULT boot TIMEOUT 10 PROMPT 1 LABEL boot KERNEL /vmlinuz APPEND initrd=/initrd LABEL=boot root=/dev/ram0 LABEL install KERNEL /vmlinuz APPEND initrd=/initrd LABEL=install root=/dev/ram0
I am switching the ownership to wei.sern.chan@intel.com as he has tested the itnel-common BSP on Romley and the patches are in queue for review.
Hi Adrian, Sorry for the delay due to heavily engage on YP1.6 activity. Romley can be build and boot on Yocto 1.6 ( Daisy branch ) which is using Kernel 3.10 on our end. Your version of syslinux.cfg,it is identical on my end. So it is fine. Due to some changes on YP1.6, can you do below:- 1. Point your poky and meta-intel layer to Daisy branch and get latest. 2. Build it. 3. Boot again with latest image. Let us know the outcome. Thanks for your patience.
Assigned to person we are requesting info from per RP.
We tested again with YP1.6 as a base and it seems to boot properly now. Closing the issue.
Setting to VERIFIED as per Adrian's comment.