dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: Alex Deucher <alexdeucher@gmail.com>, Dave Airlie <airlied@redhat.com>
Cc: Paul Menzel <paulepanter@users.sourceforge.net>,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/ttm: fix delayed ttm_bo_cleanup_refs_and_unlock delayed handling
Date: Wed, 19 Dec 2012 17:03:49 +0100	[thread overview]
Message-ID: <20121219160349.GA236@x4> (raw)
In-Reply-To: <20121219145434.GA220@x4>

On 2012.12.19 at 15:54 +0100, Markus Trippelsdorf wrote:
> On 2012.12.19 at 09:47 -0500, Alex Deucher wrote:
> 
> And the pictures get distorted on the test-webpage when I scroll up and
> down, see:
> http://trippelsdorf.de/bad.png

The picture distortion issue is caused by:

commit dd54fee7d440c4a9756cce2c24a50c15e4c17ccb
Author: Dave Airlie <airlied@redhat.com>
Date:   Fri Dec 14 21:04:46 2012 +1000

    radeon: fix regression with eviction since evict caching changes
    
    Since 0d0b3e7443bed6b49cb90fe7ddc4b5578a83a88d
    drm/radeon: use cached memory when evicting for vram on non agp
    
    evicting from TTM would try and evict to TTM instead of system,
    not so good.
    
    This should fix:
    https://bugs.freedesktop.org/show_bug.cgi?id=58272
    
    Signed-off-by: Dave Airlie <airlied@redhat.com>
    Signed-off-by: Maarten Lankhorst <maarten.lankhorst@canonical.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

Reverting the commit above "fixes" the problem.

-- 
Markus

  reply	other threads:[~2012-12-19 16:03 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-19 14:18 [PATCH] drm/ttm: fix delayed ttm_bo_cleanup_refs_and_unlock delayed handling Maarten Lankhorst
2012-12-19 14:33 ` Markus Trippelsdorf
2012-12-20 13:30   ` Alex Deucher
2012-12-20 13:45     ` Markus Trippelsdorf
2012-12-20 13:58       ` Markus Trippelsdorf
2013-01-05 10:41         ` Markus Trippelsdorf
2013-01-15 14:43           ` Michel Dänzer
2013-01-15 15:23             ` Markus Trippelsdorf
2013-01-15 15:26               ` Michel Dänzer
2013-01-15 16:32                 ` Markus Trippelsdorf
2013-01-15 17:03                   ` Markus Trippelsdorf
2013-01-16 22:36                     ` Alex Deucher
2013-01-16 23:10                       ` Markus Trippelsdorf
2013-01-17  0:18                         ` Jerome Glisse
2013-01-17  8:46                           ` Markus Trippelsdorf
2013-01-17 15:44                             ` Jerome Glisse
2013-01-17 16:10                               ` Markus Trippelsdorf
2013-01-17 17:55                                 ` Jerome Glisse
2013-01-17 18:07                                   ` Markus Trippelsdorf
2013-01-17 18:28                                 ` Jerome Glisse
2013-01-17 18:57                                   ` Markus Trippelsdorf
2012-12-19 14:41 ` Paul Menzel
2012-12-19 14:47   ` Alex Deucher
2012-12-19 14:54     ` Markus Trippelsdorf
2012-12-19 16:03       ` Markus Trippelsdorf [this message]
2012-12-19 17:21 ` Maarten Lankhorst
2012-12-19 18:40   ` Paul Menzel

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=20121219160349.GA236@x4 \
    --to=markus@trippelsdorf.de \
    --cc=airlied@redhat.com \
    --cc=alexdeucher@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=paulepanter@users.sourceforge.net \
    /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).