From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 52313] New: r600g: Linux 3.3.x broken since 30257c32
Date: Fri, 20 Jul 2012 14:37:04 +0000 [thread overview]
Message-ID: <bug-52313-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=52313
Bug #: 52313
Summary: r600g: Linux 3.3.x broken since 30257c32
Classification: Unclassified
Product: Mesa
Version: git
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: stefandoesinger@gmx.at
Since Mesa commit 30257c32910c3f7ac2b9cc24399d6be196d34d26 r600g fails to
render anything on Linux 3.3 and probably all earlier versions. An upgrade to
3.4 fixes the issue.
The output from glxinfo is:
radeon: The kernel rejected CS, see dmesg for more information.
This is accompanied by the following lines in dmesg:
[199859.400626] radeon 0000:01:00.0: forbidden register 0x00028b28 at 188
[199859.400628] [drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream !
My understanding is that Mesa is intended to remain backwards compatible with
older kernels. If this is not the case feel free to close the bug.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2012-07-20 14:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-20 14:37 bugzilla-daemon [this message]
2012-07-20 15:23 ` [Bug 52313] r600g: Linux 3.3.x broken since 30257c32 bugzilla-daemon
2012-09-03 11:23 ` 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-52313-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.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 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.