Bug 2867

Summary:	glxinfo and glxgears missing from e-menlow sato images
Product:	[Build System, Metadata & Runtime] BSPs	Reporter:	Alexandru Georgescu <alexandru.c.georgescu>
Component:	bsps-meta-intel	Assignee:	Nitin Kamble <nitin.a.kamble>
Status:	VERIFIED NOTABUG	QA Contact:
Severity:	normal
Priority:	Medium	CC:	laurentiu.serban, tom.zanussi
Version:	1.3
Target Milestone:	1.3
Hardware:	E-Menlow
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	---

Description Alexandru Georgescu 2012-07-31 13:51:12 UTC

I have the following errors when running the abat test on the e-menlow sato image:
http://autobuilder03.jf.intel.com/pub/nightly-meta-intel/20120730-2/machines/emenlow/core-image-sato-emenlow-20120730042252.hddimg

THE OUTPUT OF THE TEST:

#
Detect Xorg directory automatically...
Xorg directory is /usr
Dynamic library path check.........................
WARNING: No glxinfo found, ignore DRI checking!

[WARNING] Xorg has started!
(EE) PSB(0): the stolenBase is:0x7fc00000
(EE) PSB(0): screnIndex is:0;fbPhys is:0x7fc00000; fbsize is:0x003df000
(EE) PSB(0): Probe Address LVDSBLC_B Slave 0x58 failed.
(EE) PSB(0): has_fbdev is true
(EE) PSB(0): Probe Address LVDSBLC_B Slave 0x58 failed.
(EE) PSB(0): Probe Address LVDSBLC_B Slave 0x58 failed.
(EE) PSB(0): Probe Address LVDSBLC_B Slave 0x58 failed.
(EE) PSB(0): Probe Address LVDSBLC_B Slave 0x58 failed.
(EE) PSB(0): Probe Address LVDSBLC_B Slave 0x58 failed.
(EE) PSB(0): Probe Address LVDSBLC_B Slave 0x58 failed.
(EE) PSB(0): Probe Address LVDSBLC_B Slave 0x58 failed.
(EE) PSB(0): Probe Address LVDSBLC_B Slave 0x58 failed.
(EE) PSB(0): Probe Address LVDSBLC_B Slave 0x58 failed.
(EE) PSB(0): Probe Address LVDSBLC_B Slave 0x58 failed.
(EE) PSB(0): Probe Address LVDSBLC_B Slave 0x58 failed.
(EE) PSB(0): Probe Address LVDSBLC_B Slave 0x58 failed.
(EE) PSB(0): has_fbdev is true
(EE) PSB(0): Unable to read from SDVOCTRL_E for SDVOB slave 0x70.
(EE) PSB(0): Unable to read from SDVOCTRL_E for SDVOB slave 0x70.
(EE) PSB(0): Unable to read from SDVOCTRL_E for SDVOB slave 0x70.
(EE) PSB(0): Unable to read from SDVOCTRL_E for SDVOB slave 0x70.
(EE) PSB(0): Unable to read from SDVOCTRL_E for SDVOB slave 0x70.
(EE) PSB(0): Unable to read from SDVOCTRL_E for SDVOB slave 0x70.
(EE) PSB(0): Unable to read from SDVOCTRL_E for SDVOB slave 0x70.(EE) PSB(0): Unable to read from SDVOCTRL_E for SDVOB slave 0x70.
(EE) PSB(0): Unable to write to SDVOCTRL_E for SDVOB Slave 0x70.
(EE) PSB(0): Unable to write to SDVOCTRL_E for SDVOB Slave 0x70.
(EE) PSB(0): Unable to write to SDVOCTRL_E for SDVOB Slave 0x70.
(EE) PSB(0): Unable to read from SDVOCTRL_E for SDVOB slave 0x70.
(EE) PSB(0): Unable to write to SDVOCTRL_E for SDVOB Slave 0x70.
(EE) PSB(0): Unable to read from SDVOCTRL_E for SDVOB slave 0x70.
(EE) PSB(0): Unable to read from SDVOCTRL_E for SDVOB slave 0x70.
(EE) PSB(0): Unable to read from SDVOCTRL_E for SDVOB slave 0x70.
(EE) PSB(0): Unable to read from SDVOCTRL_E for SDVOB slave 0x70.
(EE) PSB(0): Unable to read from SDVOCTRL_E for SDVOB slave 0x70.
(EE) PSB(0): Unable to read from SDVOCTRL_E for SDVOB slave 0x70.
(EE) PSB(0): Unable to read from SDVOCTRL_E for SDVOB slave 0x70.
(EE) PSB(0): Unable to read from SDVOCTRL_E for SDVOB slave 0x70.
(EE) PSB(0): Unable to read from SDVOCTRL_E for SDVOB slave 0x70.
(EE) PSB(0): Unable to read from SDVOCTRL_E for SDVOB slave 0x70.
(EE) PSB(0): Unable to read from SDVOCTRL_E for SDVOB slave 0x70.
(EE) PSB(0): Unable to read from SDVOCTRL_E for SDVOB slave 0x70.
(EE) PSB(0): Unable to read from SDVOCTRL_E for SDVOB slave 0x70.
(EE) PSB(0): : No SDVO detected
(EE) PSB(0): Unable to write to SDVOCTRL_E for SDVOB Slave 0x70.
(EE) PSB(0): Unable to read from SDVOCTRL_E for SDVOB slave 0x70.
(EE) PSB(0): Unable to write to SDVOCTRL_E for SDVOB Slave 0x70.
(EE) PSB(0): Probe Address LVDSBLC_B Slave 0x58 failed.
(EE) PSB(0): Probe Address LVDSBLC_B Slave 0x58 failed.
(EE) PSB(0): Probe Address LVDSBLC_B Slave 0x58 failed.
(EE) PSB(0): Probe Address LVDSBLC_B Slave 0x58 failed.
ERROR in openning X server, accroding to log file: /var/log/Xorg.0.log
Start up the X server PASS!

module checking..........................
    module [intel_agp] check FAIL, please load it manually!
    module [i915] check FAIL, please load it manually!
i915 has been built in kernel!
Please ignore above error info!
module checking PASS!

glxinfo : 
run glxinfo: ....
WARNING: No glxinfo found, ignore DRI cheching!

Xorg support XVideo extension, PASS!
Xorg support VidMode extension, PASS!

 No glxgears found, skip...

Video Adaptor is Intel's, PASS!

=====================================================
ABAT test finished!
PASS 4/FAIL 0/SKIP 4
=====================================================




GLXINFO AND GLXGEARS:

root@emenlow:~/abat# which glxinfo
root@emenlow:~/abat# which glxgears

Comment 1 Darren Hart 2012-07-31 16:49:20 UTC

Something appears to have gone horribly wrong with the PSB driver.

Comment 2 Nitin Kamble 2012-08-01 04:41:35 UTC

glxgears & glxinfo are not supposed to be part of core-image-sato.

You get these test tools by adding this line to local.conf while building.

EXTRA_IMAGE_FEATURES += "tools-testapps"


Also the 3D graphics is not enabled for emenlow BSP, and no need for it's testing on emenlow.

Comment 3 Tom Zanussi 2012-08-01 05:04:01 UTC

Nitin is correct that the sato image doesn't contain glxgears, etc but tools-testapps adds it.  emenlow does have 3d graphics though, and should be tested.

Comment 4 Nitin Kamble 2012-08-01 05:09:32 UTC

Tom,

As our previous discussion/transfer on BSP testing. I remember you mentioned : For BSPs maintained by us: You should test this on the BSPs we care about 3d acceleration on:

crownbay
sugarbay
chiefriver
fri2

But not the -noemgd versions - we don't care about 3d on those.

So I thought that we do not care 3D for emenlow. Did I misunderstand you?

Thanks,
Nitin

Comment 5 Tom Zanussi 2012-08-01 05:12:15 UTC

I guess I forgot about emenlow in this case.  It doesn't use emgd but it does support 3d and I and PRC always did run glxgears on it for testing.

Comment 6 Nitin Kamble 2012-08-01 05:14:35 UTC

Tom, 
  Thanks for clarification !
Nitin

Comment 7 Laurentiu Serban 2012-08-01 11:21:22 UTC

Verified