Bug 11879 - Testimage: multiple "uvesafb" errors present in log in minnowmax on genericx86/genericx86-64
Summary: Testimage: multiple "uvesafb" errors present in log in minnowmax on genericx8...
Status: RESOLVED FIXED
Alias: None
Product: BSPs
Classification: Build System, Metadata & Runtime
Component: bsps-configuration (show other bugs)
Version: 2.4
Hardware: MinnowBoard Max Multiple
: Medium+ normal
Target Milestone: 2.4 M4
Assignee: Alejandro Hernandez
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2017-07-31 23:54 UTC by Juan Ramos
Modified: 2017-09-15 15:09 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
testimagelog Minowmax64.wic (39.88 KB, application/octet-stream)
2017-07-31 23:54 UTC, Juan Ramos 		no flags Details
testimage log_Minowmax32.wic (40.26 KB, application/octet-stream)
2017-08-01 00:00 UTC, Juan Ramos 		no flags Details
full log (41.28 KB, application/octet-stream)
2017-08-01 22:09 UTC, oscar lopez arandas 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Juan Ramos 2017-07-31 23:54:03 UTC 
Created attachment 3908 [details]
testimagelog Minowmax64.wic

STATUS: IDLE
BUILD: 2.4 M2: rc2-8e15e9b6e478f6368034519b2a8fd3c7ea71d23b
ENVIRONMENT: genericx86-64-WIC on MMAX64
Build Configuration:
BB_VERSION        = "1.35.0"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "universal"
TARGET_SYS        = "x86_64-poky-linux"
MACHINE           = "genericx86-64"
DISTRO            = "poky"
DISTRO_VERSION    = "2.3"
TUNE_FEATURES     = "m64 core2"
TARGET_FPU        = ""
meta              
meta-poky         
meta-yocto-bsp    = "HEAD:8e15e9b6e478f6368034519b2a8fd3c7ea71d23b"
STEPS TO REPRODUCE: 
  
1.- Clone poky and configure to run the automated BSP test like this:
https://wiki.yoctoproject.org/wiki/Quality_Assurance_yocto_project

2.- Download genericx86-64 core-image-sato-sdk WIC from:
https://autobuilder.yocto.io/pub/releases/yocto-2.4_M2.rc2/machines/genericx86-64/https://autobuilder.yocto.io/pub/releases/yocto-2.4_M2.rc2/machines/genericx86-64/

3.- Burn the image to a usb ando boot to it, in host type:
$bitbake core-image-sato-sdk -c testimage



EXPECTED OUTCOME: 
  
 No errors or fails should be present in logs

ACTUAL OUTCOME:
Multiple "uvesafb" errors are present in log:

uvesafb: failed to execute /sbin/v86d
uvesafb: probe of uvesafb.0 failed with error -22
uvesafb: vbe_init() failed with -22
uvesafb: Getting VBE info block failed (eax=0x4f00, err=-2)

Note: this errors are present in .hddimg and .WIC images, both x86 and x86-64.
Probably a clon of Bug 6584
Logs attached.
Comment 1 Juan Ramos 2017-08-01 00:00:34 UTC 
Created attachment 3909 [details]
testimage log_Minowmax32.wic
Comment 2 oscar lopez arandas 2017-08-01 22:09:15 UTC 
This errors is present in NUC 6i5SYH 

BUILD: 2.4 M2: rc2-8e15e9b6e478f6368034519b2a8fd3c7ea71d23b
ENVIRONMENT: genericx86-64 
Build Configuration:
BB_VERSION        = "1.35.0"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "universal"
TARGET_SYS        = "x86_64-poky-linux"
MACHINE           = "genericx86-64"
DISTRO            = "poky"
DISTRO_VERSION    = "2.3"
TUNE_FEATURES     = "m64 core2"

STEPS TO REPRODUCE: 
  
1.- Clone poky and configure to run the automated BSP test like this:
https://wiki.yoctoproject.org/wiki/Quality_Assurance_yocto_project

2.- Download genericx86-64 core-image-sato-sdk WIC from:
https://autobuilder.yocto.io/pub/releases/yocto-2.4_M2.rc2/machines/genericx86-64/https://autobuilder.yocto.io/pub/releases/yocto-2.4_M2.rc2/machines/genericx86-64/

3.- Burn the image to a usb ando boot to it, in host type:
$bitbake core-image-sato-sdk -c testimage


EXPECTED OUTCOME: 
  
 No errors or fails should be present in logs

ACTUAL OUTCOME:
Multiple "uvesafb" errors are present in log:

uvesafb: failed to execute /sbin/v86d
uvesafb: probe of uvesafb.0 failed with error -22
uvesafb: vbe_init() failed with -22
uvesafb: Getting VBE info block failed (eax=0x4f00, err=-2)
Logs attached.
Comment 3 oscar lopez arandas 2017-08-01 22:09:59 UTC 
Created attachment 3913 [details]
full log
Comment 4 Alejandro Hernandez 2017-08-28 21:48:25 UTC 
This is beign caused by:

+KERNEL_MODULE_AUTOLOAD += "uvesafb"

which was added on e8b1c653946ef921b65d47e52aea0dc530ef4286 to qemuboot-x86.inc

Still working on what the cleanest solution would be.