Bug 6076 - linux-yocto 3.10 kernel fails to boot on romley-ivb
Summary: linux-yocto 3.10 kernel fails to boot on romley-ivb
Status: VERIFIED FIXED
Alias: None
Product: BSPs
Classification: Build System, Metadata & Runtime
Component: bsps-meta-intel (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium+ major
Target Milestone: 1.6
Assignee: Adrian Dudau
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2014-03-31 13:48 UTC by Adrian Dudau
Modified: 2014-07-21 16:34 UTC (History)
6 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know


Attachments
kernel panic message when booting the romely-ivb (124.19 KB, image/jpeg)
2014-04-07 10:23 UTC, Adrian Dudau
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Adrian Dudau 2014-03-31 13:48:43 UTC
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.
Comment 1 Darren Hart 2014-03-31 16:27:23 UTC
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.
Comment 2 Adrian Dudau 2014-04-01 14:21:07 UTC
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.
Comment 3 Darren Hart 2014-04-01 16:00:11 UTC
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?
Comment 4 Adrian Dudau 2014-04-07 10:23:03 UTC
Created attachment 1898 [details]
kernel panic message when booting the romely-ivb
Comment 5 Adrian Dudau 2014-04-07 10:24:29 UTC
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
Comment 6 Ong Boon Leong 2014-05-08 15:47:27 UTC
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.
Comment 7 Wei Sern Chan 2014-05-22 09:17:31 UTC
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.
Comment 8 Stephen K Jolley 2014-06-18 17:39:34 UTC
Assigned to person we are requesting info from per RP.
Comment 9 Adrian Dudau 2014-07-01 08:33:47 UTC
We tested again with YP1.6 as a base and it seems to boot properly now. Closing the issue.
Comment 10 Stoicescu Cornel 2014-07-21 12:08:53 UTC
Setting to VERIFIED as per Adrian's comment.