Bug 1378388 - It reported failures regarding the Video test (AST2400) on 3.10.0-327.el7.ppc64le on rhcert version 2.8 and 2.9
Summary: It reported failures regarding the Video test (AST2400) on 3.10.0-327.el7.ppc...
Keywords:
Status: NEW
Alias: None
Product: Red Hat Certification Program
Classification: Red Hat
Component: redhat-certification
Version: 1.0
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Greg Nichols
QA Contact: rhcert qe
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-22 10:24 UTC by smc_cert
Modified: 2022-09-07 04:19 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)
video_output_fail.log (3.57 KB, text/plain)
2016-09-22 10:25 UTC, smc_cert
no flags Details
rhcert-results-p8dtu-20160922093727.xml.gz (4.16 MB, application/x-gzip)
2016-09-22 10:26 UTC, smc_cert
no flags Details
video_output_fail_xorg_updated.log (68.53 KB, text/plain)
2016-09-22 11:25 UTC, smc_cert
no flags Details

Description smc_cert 2016-09-22 10:24:50 UTC
Description of problem:
It reported failures regarding the Video test (AST2400) on 3.10.0-327.el7.ppc64le on rhcert version 2.8 and 2.9.


PS: Onboard ASPEED AST2400 graphic controller cannot be bring up into GUI mode(runlevel 5) on SUT on RHEL 7.2 GA

Does the video test item MUST implement under the GUI mode, this cert SUT supports TEXT mode on 3.10.0-327.el7.ppc64le only ??


[root@p8dtu ~]# uname -r
3.10.0-327.el7.ppc64le

[root@p8dtu ~]# rhcert-backend version
rhcert version 2.9, release 20160909

video /devices/pci0001:00/0001:00:00.0/0001:01:00.0/0001:02:0b.0/0001:0f:00.0/0001:10:00.0 - FAIL

[root@p8dtu ~]# lspci |grep -i vga
0001:10:00.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED Graphics Family (rev 30)

===Trimmed portion of output.log====
</output>
<output name="The X Server Test" description="Run a second X test server">
Running: xinit -- :2 
process 8859
glxgears -display :2
Error: couldn't open display :2

Error: glxgears failed, return code: 255
Killing xinit PID 8859
<summary>FAIL</summary>
</output>
<output name="Log Module and Drivers" description="Log depth, module and driver information">
Error: failed to obtain current screen resolution and color depth !
=======================================

Please refer attached log "video_output_fail.log" for details.


https://bugzilla.redhat.com/show_bug.cgi?id=1370007

Version-Release number of selected component (if applicable):


How reproducible:
Always.


Steps to Reproduce:
1.rhcert-backend run --test video
2.
3.

Actual results:
/devices/pci0001:00/0001:00:00.0/0001:01:00.0/0001:02:0b.0/0001:0f:00.0/0001:10:00.0 - FAIL

Expected results:
/devices/pci0001:00/0001:00:00.0/0001:01:00.0/0001:02:0b.0/0001:0f:00.0/0001:10:00.0 - Pass

Additional info:

Comment 1 smc_cert 2016-09-22 10:25:29 UTC
Created attachment 1203676 [details]
video_output_fail.log

Comment 2 smc_cert 2016-09-22 10:26:25 UTC
Created attachment 1203677 [details]
rhcert-results-p8dtu-20160922093727.xml.gz

Comment 3 smc_cert 2016-09-22 11:24:56 UTC
Upgrade below packages and SUT works under GUI mode successfully on 3.10.0-327.el7.ppc64le but got the failed result regarding "Video test item" still w/ same symptom (glxgears -display :2 Error: couldn't open display :2)

Please refer attached log"video_output_fail_xorg_updated.log" for details.

xorg-x11-server-Xorg-1.17.2-22.el7.ppc64le.rpm
xorg-x11-server-common-1.17.2-22.el7.ppc64le.rpm
glx-utils-8.2.0-3.el7.ppc64le.rpm
xorg-x11-utils-7.5-14.el7.ppc64le.rpm


Thanks,
Jass / Supermicro

Comment 4 smc_cert 2016-09-22 11:25:11 UTC
Created attachment 1203689 [details]
video_output_fail_xorg_updated.log

Comment 5 Rainer Koenig 2016-11-04 08:41:41 UTC
I experience a similar behaviour on Intel x86_64 architecture if the SUT is a machine with 2 physical CPU sockets. I filed a bug with a description for a bizarre workaround here: https://bugzilla.redhat.com/show_bug.cgi?id=1391841


Note You need to log in before you can comment on or make changes to this bug.