All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 72387] New: Tearing at one specific part of the screen on CAYMAN
Date: Fri, 06 Dec 2013 08:36:37 +0000	[thread overview]
Message-ID: <bug-72387-502@http.bugs.freedesktop.org/> (raw)


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

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

          Priority: medium
            Bug ID: 72387
          Assignee: dri-devel@lists.freedesktop.org
           Summary: Tearing at one specific part of the screen on CAYMAN
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: v10lator@myway.de
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: git
         Component: Drivers/Gallium/r600
           Product: Mesa

I see this with games as well as on my (composited) desktop when scrolling very
fast in firefox, for example.

Let me try to explain:
If you would cut the screen horizontally in 3 pieces the line between the
middle and the down piece is where the tearing appears. It appears even with
vsync.

I tried to capture it with gtk-rekordmydesktop but for some reason the video is
tear-free.

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

[-- Attachment #1.2: Type: text/html, Size: 2278 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-12-06  8:36 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-06  8:36 bugzilla-daemon [this message]
2013-12-06 10:44 ` [Bug 72387] Tearing at one specific part of the screen on CAYMAN bugzilla-daemon
2013-12-07 21:51 ` bugzilla-daemon
2013-12-08  8:40 ` bugzilla-daemon
2013-12-08  8:41 ` bugzilla-daemon
2013-12-08  8:42 ` bugzilla-daemon
2013-12-08 14:31 ` bugzilla-daemon
2013-12-08 15:50 ` bugzilla-daemon
2013-12-09  3:44 ` bugzilla-daemon
2013-12-09  3:48 ` bugzilla-daemon
2013-12-09 15:02 ` bugzilla-daemon
2013-12-11  4:21 ` bugzilla-daemon
2015-05-29 13:44 ` bugzilla-daemon
2015-06-01  7:21 ` bugzilla-daemon
2015-10-20 11:30 ` bugzilla-daemon
2015-10-20 11:33 ` bugzilla-daemon
2019-09-18 19:12 ` 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-72387-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.