Bug 731404 - trispd from mesa-demos not working properly
Summary: trispd from mesa-demos not working properly
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: mesa
Version: 6.3
Hardware: Unspecified
OS: Unspecified
low
unspecified
Target Milestone: rc
: ---
Assignee: Dave Airlie
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-08-17 14:28 UTC by Tomas Pelka
Modified: 2011-08-30 21:15 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-08-17 15:37:14 UTC


Attachments (Terms of Use)
screenshot (739.69 KB, image/png)
2011-08-17 14:28 UTC, Tomas Pelka
no flags Details

Description Tomas Pelka 2011-08-17 14:28:34 UTC
Created attachment 518692 [details]
screenshot

Description of problem:
SSIA plus 100% CPU consumption

Version-Release number of selected component (if applicable):
xorg-x11-drv-ati-6.14.2-6.el6.x86_64
kernel-2.6.32-184.el6.x86_64
mesa-dri-drivers-7.11-1.el6.x86_64
mesa-libGL-7.11-1.el6.x86_64
mesa-libGLU-devel-7.11-1.el6.x86_64
mesa-libGLU-7.11-1.el6.x86_64
mesa-libGLw-6.5.1-10.el6.x86_64
mesa-demos-7.11-1.el6.x86_64
mesa-libOSMesa-7.11-1.el6.x86_64

How reproducible:
100%

Steps to Reproduce:
1. run /usr/lib64/mesa/trispd
2.
3.
  
Actual results:
not rendered properly

Expected results:


Additional info:

Comment 1 Tomas Pelka 2011-08-17 14:29:26 UTC
Forgot to add


18:00.0 VGA compatible controller [0300]: ATI Technologies Inc RV620 [ATI FireGL V3700] [1002:95cc] (prog-if 00 [VGA controller])
	Subsystem: Hewlett-Packard Company Device [103c:1b03]
	Physical Slot: 4
	Flags: bus master, fast devsel, latency 0, IRQ 29
	Memory at e0000000 (64-bit, prefetchable) [size=256M]
	Memory at f0100000 (64-bit, non-prefetchable) [size=64K]
	I/O ports at 1100 [size=256]
	[virtual] Expansion ROM at f0120000 [disabled] [size=128K]
	Capabilities: <access denied>
	Kernel driver in use: radeon
	Kernel modules: radeon

Comment 3 Dave Airlie 2011-08-17 15:37:14 UTC
that looks exactly like it does with the sw renderer here. and it is meant to use all the CPU it tries to render as many triangles as it can in a tight loop.

I'll notabug this unless you can point what is actually rendering wrong compared to LIBGL_ALWAYS_SOFTWARE=y


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