Bug 8283

Summary: E-Menlow genericx86 USB install does not work
Product: [Build System, Metadata & Runtime] BSPs Reporter: Cristina Agurida <cristina-danielax.agurida>
Component: bsps-runtimeAssignee: Saul Wold <sgw>
Status: RESOLVED FIXED QA Contact: Cristina Agurida <cristina-danielax.agurida>
Severity: minor    
Priority: Medium CC: alexandru.c.georgescu, sgw, yp.kernel.watcher, yp.watcher
Version: 1.9   
Target Milestone: 2.0   
Hardware: E-Menlow   
OS: x86   
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
image none

Description Cristina Agurida 2015-09-11 10:20:41 UTC
Created attachment 2726 [details]
image

Branch: 1.9 master
POKY: d4585fa23d56a58c583ee33db067a23177a936b1
ENVIRONMENT: genericx86 
HARDWARE: E-Menlow
IMAGE: core-image-sato-sdk

STEPS TO REPRODUCE: 
1. plugin usb which contains a core-image-sato-sdk image, genericx86 environment 
2. configure device BIOS to firstly boot from USB if necessary
3. boot the device and select option "Install"  from boot menu

EXPECTED OUTCOME: 
Installed system can boot up

ACTUAL OUTCOME:
"sh: can't access tty; job control turned off" error appears when try to install the image.

See attached image for details.
Comment 1 Saul Wold 2015-09-21 15:31:25 UTC
It appears that the abat test is attempting to start X on the current display 
and failing due to X/Sato already running on that display, this will show as a 
failure, please confirm that you run ABAT under a terminal window and have run 
it like this before?  I can not access the actual abat test script and the 
testopia test case (269) does not provide the information about where you run 
it from.

The screen shot very clearly shows the Fatal server error that a server is 
already active for display 0, this will cause a cascade failure for the 
remaining tests.
Comment 2 Saul Wold 2015-09-21 15:33:29 UTC
last comment was for a different bug, sorry for the noise, I have reproduced 
this issue, it appear that the kernel is not seeing the internal disk
Comment 3 Saul Wold 2015-09-28 13:58:24 UTC
Added CONFIG_PATA_SCH, so older hardware would work.

http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/commit/?id=5e218aeacace801c4f01a1db8c99ac8a51421661