All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 79488] New: Checkerboard tearing on Radeon card
Date: Sat, 31 May 2014 18:11:44 +0000	[thread overview]
Message-ID: <bug-79488-502@http.bugs.freedesktop.org/> (raw)


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

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

          Priority: medium
            Bug ID: 79488
          Assignee: dri-devel@lists.freedesktop.org
           Summary: Checkerboard tearing on Radeon card
          Severity: normal
    Classification: Unclassified
                OS: All
          Reporter: dan.doel@gmail.com
          Hardware: Other
            Status: NEW
           Version: unspecified
         Component: DRM/Radeon
           Product: DRI

Created attachment 100211
  --> https://bugs.freedesktop.org/attachment.cgi?id=100211&action=edit
dmesg while the machine is in the 'tearing' state

For several months now, I've occasionally run into situations where my screen
displays a strange artifact or tearing pattern. It is only visible when things
are changing, of course, and it looks like the monitor is divided into small
squares, and two different 'frames' are drawn alternately. Here is a video of
the problem I took back at the end of February:

  https://www.youtube.com/watch?v=e2T8BeE0j74

I've just encountered this again, and it reminded me to finally post a bug.

You'll notice that the video was recorded on a cell phone. I tried using a
desktop recorder (the one built into gnome-shell) and the resulting video did
not display the artifacts. So it would seem to be happening at a level below
what capture can detect.

I'll attach dmesg and xorg logs from when the problem is happening. You'll see
that there are lots of page flip errors in both. However, I think that actually
might be a red herring. Doing a tail -f on the logs, I can cause artifacts to
display (for instance, selecting a different channel in my irc client, causing
highlighting to change, which briefly displays checkerboard highlights) without
a corresponding xorg error. And I also frequently see those errors accompanied
by ordinary tearing. But I can't definitively say that they aren't related,
either.

I'm using:

  mesa from git as of about a week ago (rev 63069)
  latest glamor (as of 2014-03-13)
  xf86-video-ati 7.3.0
  kernel 3.14.4

But this has been happening for significantly longer than just those versions.

I have a Radeon HD 7870 (pitcairn).

I'm not certain that I've assigned this bug to the right project, although at
least some of the visible errors involve drm. Apologies if it's the fault of
something else, though.

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

[-- Attachment #1.2: Type: text/html, Size: 3974 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:[~2014-05-31 18:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-31 18:11 bugzilla-daemon [this message]
2014-05-31 18:13 ` [Bug 79488] Checkerboard tearing on Radeon card bugzilla-daemon
2019-11-19  8:50 ` 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-79488-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.