dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 43209] PAE and radeon integrated rs690 (x1200) prevents dri
Date: Tue,  4 Sep 2012 04:35:19 +0000 (UTC)	[thread overview]
Message-ID: <20120904043519.5F5F711FB3A@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-43209-2300@https.bugzilla.kernel.org/>

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


Luis Montes <lamr64@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |lamr64@gmail.com




--- Comment #2 from Luis Montes <lamr64@gmail.com>  2012-09-04 04:35:19 ---
Same here, on a 3.2.0-29-generic-pae kernel with a PCIe radeon:
VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Turks [Radeon
HD 6570]
I get:
[drm:r600_ring_test] *ERROR* radeon: ring test failed
(scratch(0x8504)=0xCAFEDEAD)
radeon 0000:01:00.0: disabling GPU acceleration

I don't get acceleration, but other than that, the system works reasonably
well, so that might be the reason some people don't see the problem?

There was a similar report on the lkml about a year ago, but I tried a similar
patch to that described in there and it caused a panic.

https://lkml.org/lkml/2011/6/3/277

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

  parent reply	other threads:[~2012-09-04  4:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-43209-2300@https.bugzilla.kernel.org/>
2012-05-12  0:20 ` [Bug 43209] PAE and radeon integrated rs690 (x1200) prevents dri bugzilla-daemon
2012-09-04  4:35 ` bugzilla-daemon [this message]
2015-02-19 17:34 ` 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=20120904043519.5F5F711FB3A@bugzilla.kernel.org \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).