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 52491] New: radeon massive screen corruption BARTS HD6870
Date: Tue,  8 Jan 2013 18:42:53 +0000 (UTC)	[thread overview]
Message-ID: <bug-52491-2300@https.bugzilla.kernel.org/> (raw)

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

           Summary: radeon massive screen corruption BARTS HD6870
           Product: Drivers
           Version: 2.5
    Kernel Version: 3.8-rc
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: high
          Priority: P1
         Component: Video(DRI - non Intel)
        AssignedTo: drivers_video-dri@kernel-bugs.osdl.org
        ReportedBy: maxijac@free.fr
        Regression: No


Created an attachment (id=90801)
 --> (https://bugzilla.kernel.org/attachment.cgi?id=90801)
return to desktop after bad rendering

Hi,

I'm experiencing a major rendering corruption with linux 3.8 and my HD 6870.

software:
latest kernel from linus as of 2013-08-01
latest mesa git as of 2013-08-01
latest llvm from tstellar git as of 2013-08-01
latest DDX from git as of 2013-08-01
libdrm 2.4.40

Symptoms:

I triggered this several times running Heroes of Newerth. When a match starts,
sometimes The textures are all black, or sometimes my cursor is missing.
(It looks like my LLVM-enabled for the glsl compiler builds of mesa trigger the
black textures more often)

When this happens, quitting the game and returning to my desktop, everything is
garbled, things do not refresh correctly. See screenshot.

keeping the same userland and just downgrading to linux 3.7 solves everything.

Nothing gets added to dmesg...

I don't have much time for bisecting this, I'll try asap but it won't be before
some days, so if someone has similar hardware, please try to reproduce it. HoN
is free to play and natively runs on linux. (http://www.heroesofnewerth.com)

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

             reply	other threads:[~2013-01-08 18:42 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-08 18:42 bugzilla-daemon [this message]
2013-01-08 18:45 ` [Bug 52491] radeon massive screen corruption BARTS HD6870 bugzilla-daemon
2013-01-08 18:45 ` bugzilla-daemon
2013-01-10 23:00 ` bugzilla-daemon
2013-01-12 18:27 ` bugzilla-daemon
2013-01-12 22:27 ` bugzilla-daemon
2013-01-12 22:41 ` bugzilla-daemon
2013-01-12 23:15 ` bugzilla-daemon
2013-01-12 23:19 ` bugzilla-daemon
2013-01-15 14:36 ` bugzilla-daemon
2013-01-15 17:37 ` bugzilla-daemon
2013-01-15 19:26 ` bugzilla-daemon
2013-01-15 19:38 ` bugzilla-daemon
2013-01-15 20:57 ` bugzilla-daemon
2013-01-16 22:31 ` bugzilla-daemon
2013-01-17  0:20 ` bugzilla-daemon
2013-01-17 19:26 ` bugzilla-daemon
2013-01-26 10:50 ` bugzilla-daemon
2013-01-27 14:04 ` bugzilla-daemon
2013-03-05 14:41 ` 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-52491-2300@https.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).