Bug 799681

Summary: No GPU acceleration - drm ring test failed
Product: [Fedora] Fedora Reporter: David Rees <drees76>
Component: xorg-x11-drv-atiAssignee: Jérôme Glisse <jglisse>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 16CC: bugzilla, xgl-maint
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-05-10 05:31:51 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
dmesg none

Description David Rees 2012-03-04 08:39:30 UTC
Created attachment 567376 [details]
dmesg

Description of problem:
The radeon driver does not enable GPU acceleration meaning only fallback mode is available with Gnome 3.

Version-Release number of selected component (if applicable):
xorg-x11-drv-ati-6.14.3-4.20120201git36c190671.fc16.x86_64
kernel-3.2.9-1.fc16.x86_64

How reproducible:
Every time

Steps to Reproduce:
1. Just boot up.
  
Actual results:
drm/kernel reports these errors on boot (will attach entire dmesg):
[    2.320600] radeon 0000:01:05.0: WB enabled
[    2.320693] [drm] Loading RS690/RS740 Microcode
[    2.326946] [drm] radeon: ring at 0x00000000A0001000
[    2.487530] [drm:r100_ring_test] *ERROR* radeon: ring test failed (scratch(0x15E4)=0xCAFEDEAD)
[    2.487598] [drm:r100_cp_init] *ERROR* radeon: cp isn't working (-22).
[    2.487653] radeon 0000:01:05.0: failed initializing CP (-22).
[    2.487705] radeon 0000:01:05.0: Disabling GPU acceleration
[    2.487875] [drm] radeon: cp finalized

Expected results:
Expect GPU acceleration to work.

Comment 1 Jason Smith 2012-05-09 01:01:28 UTC
    Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue. 

    Please attach your X server config file (/etc/X11/xorg.conf), X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed text/plain file attachments using the bugzilla file attachment link above called "Add an attachment". 

    Could you please also try to run without any /etc/X11/xorg.conf whatsoever and let X11 autodetect your display and video card? Attach to this bug /var/log/Xorg.0.log from this attempt as well, please. 

    We will review this issue again once you've had a chance to attach this information. 

    Thank you in advance. 



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 2 Jason Smith 2012-05-09 01:06:43 UTC
Apologies for the delayed response to this bug as well, if this has since been resolved, please reply & I will update this bug accordingly.

Comment 3 David Rees 2012-05-09 06:26:49 UTC
Unfortunately, I have since replaced the hardware that generated this error, so we can probably close this bug now.

Comment 4 Jason Smith 2012-05-10 05:31:51 UTC
We appreciate the response Mr. Rees, I have checked my ATI hardware and 3D acceleration is enabled with successful tests.  Per your response I will close this bug for now, please re-open should it duplicate, and thanks again.

Jason
-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers