From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 49632] New: radeon: The kernel rejected CS,
Date: Tue, 08 May 2012 04:24:24 +0000 [thread overview]
Message-ID: <bug-49632-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=49632
Bug #: 49632
Summary: radeon: The kernel rejected CS,
Classification: Unclassified
Product: Mesa
Version: git
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: critical
Priority: medium
Component: Drivers/Gallium/r600
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: execute.method@gmail.com
Created attachment 61215
--> https://bugs.freedesktop.org/attachment.cgi?id=61215
glxgears apitrace 5-8-12
glxgears:
radeon: The kernel rejected CS, see dmesg for more information.
chromium --enable-webgl --ignore-gpu-blacklist:
radeon: The kernel rejected CS, see dmesg for more information.
EE r600_pipe.c:78 r600_create_fence - r600: too many concurrent fences
dmesg output:
[ 1306.131363] radeon 0000:01:00.0: forbidden register 0x00028354 at 166
[ 1306.131366] [drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream !
Computer Info:
Linux 3.3.4-2-ARCH
0.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RV730XT
[Radeon HD 4670]
model name : AMD FX(tm)-6100 Six-Core Processor
cpu MHz : 4013.411
model name : AMD FX(tm)-6100 Six-Core Processor
cpu MHz : 4013.411
model name : AMD FX(tm)-6100 Six-Core Processor
cpu MHz : 4013.411
model name : AMD FX(tm)-6100 Six-Core Processor
cpu MHz : 4013.411
model name : AMD FX(tm)-6100 Six-Core Processor
cpu MHz : 4013.411
model name : AMD FX(tm)-6100 Six-Core Processor
cpu MHz : 4013.411
X.Org version: 1.12.1
dimensions: 1920x1080 pixels (508x285 millimeters)
depth of root window: 24 planes
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
--
OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD RV730
OpenGL version string: 2.1 Mesa 8.1-devel
OpenGL shading language version string: 1.30
OpenGL extensions:
GL_ARB_multisample, GL_EXT_abgr, GL_EXT_bgra, GL_EXT_blend_color,
GL_EXT_blend_minmax, GL_EXT_blend_subtract, GL_EXT_copy_texture,
Mesa and DDX built from git, tested for a few weeks (I'm a busy man).
Started when updated/rebuilt on 4-18-12. Built again on 5-6-12.
Official packages work.
Reproduciblility: Permanent
Similar to/Same as: https://bugs.freedesktop.org/show_bug.cgi?id=47039
--
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-05-08 11:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-08 4:24 bugzilla-daemon [this message]
2012-05-08 4:56 ` [Bug 49632] radeon: The kernel rejected CS, bugzilla-daemon
2012-05-08 11:24 ` bugzilla-daemon
2012-05-08 11:38 ` bugzilla-daemon
2012-05-08 11:39 ` bugzilla-daemon
2012-05-08 12:51 ` bugzilla-daemon
2012-05-08 19:36 ` bugzilla-daemon
2012-05-09 10:55 ` bugzilla-daemon
2012-05-09 11:15 ` bugzilla-daemon
2012-05-09 13:14 ` bugzilla-daemon
2012-05-09 13:36 ` bugzilla-daemon
2012-08-08 19:10 ` bugzilla-daemon
2012-11-02 12:58 ` 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-49632-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 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).