All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 30102] New: Radeon : ring test failed
Date: Mon, 28 Feb 2011 16:28:40 GMT	[thread overview]
Message-ID: <bug-30102-2300@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=30102

           Summary: Radeon : ring test failed
           Product: Drivers
           Version: 2.5
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - non Intel)
        AssignedTo: drivers_video-dri@kernel-bugs.osdl.org
        ReportedBy: b747xx@gmail.com
        Regression: No


Created an attachment (id=49622)
 --> (https://bugzilla.kernel.org/attachment.cgi?id=49622)
dmesg

On the radoen module load, I got this error:

[    9.874444] [drm:r600_ring_test] *ERROR* radeon: ring test failed
(scratch(0x8504)=0xCAFEDEAD)
[    9.874447] radeon 0000:01:05.0: disabling GPU acceleration
[    9.875771] radeon 0000:01:05.0: ffff88043c78dc00 unpin not necessary

This is intermittent. I got theses error two weeks ago and it vanish after a
reboot about 1 week ago. The video acceleration was working perfectly until
yesterday reboot (adding an option in the kernel) and now the problem is back.

After the problem came back, I tried booting on the 3 others kernels I used
this week (when it was working correctly) and the problem is still there with
them.

I have attached the dmesg and my .config if this can help find the problem.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

------------------------------------------------------------------------------
Free Software Download: Index, Search & Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev 
--

             reply	other threads:[~2011-02-28 16:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-28 16:28 bugzilla-daemon [this message]
2011-02-28 16:29 ` [Bug 30102] Radeon : ring test failed bugzilla-daemon
2011-02-28 16:31 ` bugzilla-daemon
2011-02-28 16:32 ` bugzilla-daemon
2011-02-28 16:32 ` bugzilla-daemon
2011-02-28 17:23 ` bugzilla-daemon
2011-03-08 17:45 ` [Bug 30102] [RADEON:KMS:RS780:CP] " bugzilla-daemon
2012-08-17 10:58 ` bugzilla-daemon
2013-01-19  5:51 ` bugzilla-daemon
2013-01-19 15:57 ` bugzilla-daemon
2013-01-20  8:09 ` bugzilla-daemon
2013-01-20 14:40 ` bugzilla-daemon
2013-01-21  3:05 ` bugzilla-daemon
2013-01-21 21:06 ` bugzilla-daemon
2014-09-02 21:16 ` bugzilla-daemon
2014-09-03  2:03 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-30102-2300@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.