All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 59015] New: Steam Beta: Graphical Corruption in certain parts of application tied to "kernel rejected CS" messages
Date: Fri, 04 Jan 2013 08:48:39 +0000	[thread overview]
Message-ID: <bug-59015-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1851 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=59015

          Priority: medium
            Bug ID: 59015
          Assignee: dri-devel@lists.freedesktop.org
           Summary: Steam Beta: Graphical Corruption in certain parts of
                    application tied to "kernel rejected CS" messages
          Severity: major
    Classification: Unclassified
                OS: Linux (All)
          Reporter: adam.jorgensen.za@gmail.com
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: 9.0
         Component: Drivers/Gallium/radeonsi
           Product: Mesa

Created attachment 72495
  --> https://bugs.freedesktop.org/attachment.cgi?id=72495&action=edit
Major Graphical Corruption Occurring in Windows that are not Maximised

I am participating in the Steam Linux Beta and am experiencing graphical
corruption as captured in the screenshots attached to this ticket.

By starting Steam from the command-line I was able to observe logging messages
and noticed that every time a graphical corruption artifact occurs the
application outputs the message:

"radeon: The kernel rejected CS, see dmesg for more information."

An examination of dmesg reveals messages as follows:

"
[ 2491.179581] radeon 0000:02:00.0: r600_cs_track_validate_cb invalid tiling 6
for 0 (0x08110668)
[ 2491.179588] radeon 0000:02:00.0: r600_packet3_check:1913 invalid cmd stream
566
[ 2491.179592] [drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream !
"

Relevant system info:

1.6ghz Core i7 CPU
8gb DDR3 RAM
Radeon HD 4570 with 512mb DDR2 VRAM using open-source XF86 ATI 7.0.0 drivers
10gb free on root, 30+gb free on home
Kernel 3.6, X.org 1.12.4, KDE 4.9.4 running with OpenGL Compositing
Primary display is 1440x900 laptop LCD, secondary is 24" 1920x1080 LCD

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3465 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2013-01-04  8:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-04  8:48 bugzilla-daemon [this message]
2013-01-04  8:50 ` [Bug 59015] Steam Beta: Graphical Corruption in certain parts of application tied to "kernel rejected CS" messages bugzilla-daemon
2013-01-04  8:52 ` bugzilla-daemon
2013-01-04  8:55 ` bugzilla-daemon
2013-01-04 12:16 ` bugzilla-daemon
2013-01-04 12:17 ` bugzilla-daemon
2013-01-04 12:19 ` bugzilla-daemon
2013-01-04 13:55 ` bugzilla-daemon
2013-01-04 13:57 ` bugzilla-daemon
2013-01-04 13:59 ` bugzilla-daemon
2013-01-04 13:59 ` bugzilla-daemon
2013-01-04 14:06 ` bugzilla-daemon
2013-01-05  5:35 ` bugzilla-daemon
2013-01-05 12:51 ` 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-59015-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.