Bug 105730

Summary: [llvmpipe] 109 piglit failures, 19264 crashes on ppc (ppc64, mesa-18.0.0)
Product: Mesa Reporter: erhard_f
Component: Mesa coreAssignee: mesa-dev
Status: RESOLVED WONTFIX QA Contact: mesa-dev
Severity: normal    
Priority: medium    
Version: git   
Hardware: PowerPC   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments: results from 'pigllit run all'
log of the crashes (via journalctl -k)
html summary from 'pigllit run all'
results from 'pigllit run all' (18.0.0)
html summary from 'pigllit run all' (18.0.0)

Description erhard_f 2018-03-24 14:48:51 UTC
Created attachment 138337 [details]
results from 'pigllit run all'

My G5 had some fun running piglit with llvmpipe on Big Endian ppc64. Just wanted to share the results.

# glxinfo | grep -i opengl
OpenGL vendor string: VMware, Inc.
OpenGL renderer string: llvmpipe (LLVM 5.0, 128 bits)
OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.0.0-rc5
OpenGL core profile shading language version string: 3.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 18.0.0-rc5
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.0 Mesa 18.0.0-rc5
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
OpenGL ES profile extensions:

# ./piglit run -s sanity results/sanity
[1/1] pass: 1  
Thank you for running Piglit!
Results have been written to /root/build/piglit/results/sanity
Comment 1 erhard_f 2018-03-24 14:50:42 UTC
Created attachment 138338 [details]
log of the crashes (via journalctl -k)
Comment 2 erhard_f 2018-03-24 14:52:23 UTC
Created attachment 138339 [details]
html summary from 'pigllit run all'
Comment 3 erhard_f 2018-03-29 18:37:05 UTC
Re-run of the piglit suite with 18.0.0:

T801 ~/build/piglit # ./piglit run sanity results/sanity
[1/1] pass: 1  
Thank you for running Piglit!
Results have been written to /root/build/piglit/results/sanity

T801 ~/build/piglit # ./piglit run all results/OpenGL_all_llvm
Skipping GL_ARB_gpu_shader5 tests
[53127/53127] skip: 23711, pass: 10043, fail: 109, crash: 19264   
Thank you for running Piglit!                                  
Results have been written to /root/build/piglit/results/OpenGL_all_llvm

ef@T801 ~ $ glxinfo | grep -i opengl
OpenGL vendor string: VMware, Inc.
OpenGL renderer string: llvmpipe (LLVM 5.0, 128 bits)
OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.0.0
OpenGL core profile shading language version string: 3.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 18.0.0
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.0 Mesa 18.0.0
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
OpenGL ES profile extensions:
Comment 4 erhard_f 2018-03-29 18:38:12 UTC
Created attachment 138432 [details]
results from 'pigllit run all' (18.0.0)
Comment 5 erhard_f 2018-03-29 19:29:17 UTC
Created attachment 138435 [details]
html summary from 'pigllit run all' (18.0.0)
Comment 6 Timothy Arceri 2018-04-10 05:17:13 UTC
(In reply to erhard_f from comment #0)
> Created attachment 138337 [details]
> results from 'pigllit run all'
> 
> My G5 had some fun running piglit with llvmpipe on Big Endian ppc64. Just
> wanted to share the results.
> 

Thanks for your interest in Mesa but unless you are willing to create patches this information is not all that for tracking in a bug report. Things change fast and anyone interested in fixing it can just run piglit to get the latests results.

With this is mind I'm going to close this bug report. If you wish to discuss Big Endian support the mailing list or IRC are probably better forums.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.