From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: "Michel Dänzer" <michel@daenzer.net>,
"Jerome Glisse" <jglisse@redhat.com>
Cc: Dave Airlie <airlied@redhat.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] drm/ttm: fix delayed ttm_bo_cleanup_refs_and_unlock delayed handling
Date: Tue, 15 Jan 2013 17:32:02 +0100 [thread overview]
Message-ID: <20130115163202.GA220@x4> (raw)
In-Reply-To: <1358263615.29800.32.camel@thor.local>
On 2013.01.15 at 16:26 +0100, Michel Dänzer wrote:
> On Die, 2013-01-15 at 16:23 +0100, Markus Trippelsdorf wrote:
> > On 2013.01.15 at 15:43 +0100, Michel Dänzer wrote:
> > > On Sam, 2013-01-05 at 11:41 +0100, Markus Trippelsdorf wrote:
> > > > On 2012.12.20 at 14:58 +0100, Markus Trippelsdorf wrote:
> > > > >
> > > > > And just in case it got lost in the noise yesterday:
> > > > > The image corruption is caused by Dave's commit:
> > > > >
> > > > > 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
> > > > >
> > > > > Reverting it 'fixes' the issue.
> > > >
> > > > Ping.
> > > > The issue still happens with todays Linus git tree.
> > >
> > > Does the corruption also occur with
> > > dd54fee7d440c4a9756cce2c24a50c15e4c17ccb applied manually on top of
> > > 0d0b3e7443bed6b49cb90fe7ddc4b5578a83a88d?
> >
> > No.
>
> So, can you bisect which change between those two actually introduced
> the corruption?
86a1881d08f65a42c17071a59c0088dbe2870246 is the first bad commit
commit 86a1881d08f65a42c17071a59c0088dbe2870246
Author: Jerome Glisse <jglisse@redhat.com>
Date: Wed Dec 12 16:43:15 2012 -0500
drm/radeon: fix fence driver for dma ring when wb is disabled
The dma ring can't write to register thus have to write to memory
its fence value. This ensure that it doesn't try to use scratch
register for dma ring fence driver.
Should fix:
https://bugs.freedesktop.org/show_bug.cgi?id=58166
Signed-off-by: Jerome Glisse <jglisse@redhat.com>
Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
--
Markus
next prev parent reply other threads:[~2013-01-15 16:32 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 [this message]
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
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=20130115163202.GA220@x4 \
--to=markus@trippelsdorf.de \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jglisse@redhat.com \
--cc=michel@daenzer.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).