Created attachment 3764 [details] LSB Yocto project screen STATUS: IDLE BUILD: 2.3: rc1-meta-intel-3e655f9c7f0f4f778dc9eedd9f7405fc84b4c9ad ENVIRONMENT: corei7-64_lsb_CherryHill Build Configuration: BB_VERSION = "1.34.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "intel-corei7-64" DISTRO = "poky-lsb" DISTRO_VERSION = "2.3" TUNE_FEATURES = "m64 corei7" TARGET_FPU = "" meta meta-poky meta-yocto-bsp = "HEAD:3e655f9c7f0f4f778dc9eedd9f7405fc84b4c9ad" meta-intel = "HEAD:3afa94c979c984b978142170b8dbe6533ab8536c" Hardware spec. system serial: GPEMDP4506003 PCB: BRASSWELL RVP CRB FAB2 [MB/DT] 25X27 TYPE3 SoC MB SERIAL: SPBS43900476 8006254 O-01 Rev. A Other Tags: SAS GK POLAND OTC BSW eNB C0 SOC 25X27-F6XF 2R4382279M00730 STEPS TO REPRODUCE: 1.-Download the lsb image: http://yocto-ab-master.jf.intel.com/pub/releases/yocto-2.3.rc1/machines/intel-corei7-64-lsb/core-image-lsb-intel-corei7-64.hddimg and burn to a USB. 2.- Boot the image in a Cherryhill ACTUAL OUTCOME: The boot stops in the Yocto project screen. Screenshot attached. EXPECTED OUTCOME: The system boot to the Yocto lsb image. Note: Tested the previous meta-intel lsb image and boot ok. : It is possible to access system by ssh from remote machine.
Tested the same image that was used in cherryHill in the NUC and works well STATUS: IDLE BUILD: 2.3: rc1-meta-intel-3e655f9c7f0f4f778dc9eedd9f7405fc84b4c9ad ENVIRONMENT: corei7-64_lsb_NUC6I5SYH Build Configuration: BB_VERSION = "1.34.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "intel-corei7-64" DISTRO = "poky-lsb" DISTRO_VERSION = "2.3" TUNE_FEATURES = "m64 corei7" TARGET_FPU = "" meta meta-poky meta-yocto-bsp = "HEAD:3e655f9c7f0f4f778dc9eedd9f7405fc84b4c9ad" meta-intel = "HEAD:3afa94c979c984b978142170b8dbe6533ab8536c" STEPS TO REPRODUCE: 1.-Tested the same image that was used in cherryHill in the NUC and works well ACTUAL OUTCOME: The image boots well to LSB. EXPECTED OUTCOME:The image boots well to LSB
(In reply to comment #0) > Created attachment 3764 [details] > LSB Yocto project screen > > STATUS: IDLE > BUILD: 2.3: rc1-meta-intel-3e655f9c7f0f4f778dc9eedd9f7405fc84b4c9ad > ENVIRONMENT: corei7-64_lsb_CherryHill > Build Configuration: > BB_VERSION = "1.34.0" > BUILD_SYS = "x86_64-linux" > NATIVELSBSTRING = "universal" > TARGET_SYS = "x86_64-poky-linux" > MACHINE = "intel-corei7-64" > DISTRO = "poky-lsb" > DISTRO_VERSION = "2.3" > TUNE_FEATURES = "m64 corei7" > TARGET_FPU = "" > meta > meta-poky > meta-yocto-bsp = "HEAD:3e655f9c7f0f4f778dc9eedd9f7405fc84b4c9ad" > meta-intel = "HEAD:3afa94c979c984b978142170b8dbe6533ab8536c" > Hardware spec. > system serial: GPEMDP4506003 > PCB: BRASSWELL RVP CRB FAB2 > [MB/DT] 25X27 TYPE3 SoC > MB SERIAL: SPBS43900476 > 8006254 O-01 Rev. A > > Other Tags: > SAS GK POLAND > OTC BSW eNB C0 SOC 25X27-F6XF > 2R4382279M00730 > > STEPS TO REPRODUCE: > 1.-Download the lsb image: > http://yocto-ab-master.jf.intel.com/pub/releases/yocto-2.3.rc1/machines/ > intel-corei7-64-lsb/core-image-lsb-intel-corei7-64.hddimg and burn to a USB. > 2.- Boot the image in a Cherryhill > > ACTUAL OUTCOME: The boot stops in the Yocto project screen. Screenshot > attached. > EXPECTED OUTCOME: The system boot to the Yocto lsb image. > > Note: Tested the previous meta-intel lsb image and boot ok. > The BIOS version is: BRAS.X64.X097.R00
It will actually boot occasionally (about one in ten attempts), but its not consistent at all. I think it is some sort of race between udev and the kernel. When I disabled the splash screen, I found that starting udev was consistently one of the last things to happen before hanging. To try to get more information, I added "--debug" to the udevadm commands in /etc/init.d/udev. However, instead of failing and giving me more information, adding the debug option instead caused the issue to go away completely, with the board successfully booting on every attempt. Changing to a 4.8 or 4.10 kernel also caused it to boot every attempt, with 4.4 still failing.
This fails on a specific hardware platform that is not actually public, when tested on other cherry trail hardware it does work, I am going to close this and we are re-visiting the hardware matrix for 2.4