Created attachment 87730 [details] dmesg Driver Stack Details : ====================== 1) Kernel-3.10.5-031005-generic 2) drm-2.4.46 3) Mesa-2.1 Mesa-9.3.0-devel(git-8bc7673) 4) Xorg-server-1.12.99.905 5) xf86-video-ati-Git master 6) glamor-0.5.1 7) LLVM-3.3 System Configuration: ===================== Asic : Pitcairn Pro-6819 O.S. : Ubuntu-13.04 (64 bit) Steps to Reproduce: =================== 1) Install Specviewperf10 with Phoronix Test suite 2) phoronix-test-suite run specviewperf10 and select proe-04 Observation : =========== 1) Proe-4 fails to run 2) The system becomes unresponsive after few minutes.
Created attachment 87731 [details] Xorg.log
I notice in dmesg that UVD fails to initialize. Is the RLC microcode up to date?
Created attachment 87780 [details] dmesg-updated
The issue is still reproduced after updating the firmware. Attached is the updated dmesg log with message "[drm] UVD initialized sucessfully". Additional Info : The issue is not observed with latest Closed source "fglrx" driver
I finally figured out why PTS failed to install the specviewperf10 test for me (the installation hangs with ccache). The proe-04 test only draws the splash screen here, after that I get lines like: [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -12! in dmesg, indicating the kernel fails to process the drawing command streams, probably due to running out of VRAM or GTT memory. Does that match what you're seeing?
samit vats, Ubuntu 13.04 reached EOL on May January 27, 2014. For more on this, please see https://wiki.ubuntu.com/Releases. If this is reproducible in a supported release, it will help immensely if you filed a new report with Ubuntu by ensuring you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information running the following from a terminal: ubuntu-bug xorg Also, please feel free to subscribe me to it. For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.
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.