From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: Jerome Glisse <j.glisse@gmail.com>,
Antti Palosaari <crope@iki.fi>, Borislav Petkov <bp@alien8.de>,
Shuah Khan <shuahkhan@gmail.com>,
Andy Furniss <andyqos@ukfsn.org>,
Alex Deucher <alexander.deucher@amd.com>,
dri-devel@lists.freedesktop.org,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: radeon 0000:02:00.0: GPU lockup CP stall for more than 10000msec
Date: Thu, 3 Jan 2013 09:33:22 +0100 [thread overview]
Message-ID: <20130103083322.GA230@x4> (raw)
In-Reply-To: <CADnq5_OuhJordwCQArknpdvzYLryouZ+u+a+tm37n3K+hmB9uw@mail.gmail.com>
On 2013.01.02 at 18:37 -0500, Alex Deucher wrote:
> On Wed, Jan 2, 2013 at 5:38 PM, Markus Trippelsdorf
> <markus@trippelsdorf.de> wrote:
> > On 2013.01.02 at 17:31 -0500, Jerome Glisse wrote:
> >> Please affected people can you test if patch :
> >> http://people.freedesktop.org/~glisse/0003-drm-radeon-fix-dma-copy-on-r6xx-r7xx-evergen-ni-si-g.patch
> >>
> >> Fix the issue, you need to make sure you don't have the patch that
> >> disable dma on r6xx ie that line 977-978 & 1061-1062 in radeon_asic.c
> >> is :
> >> .copy = &r600_copy_dma,
> >> .copy_ring_index = R600_RING_TYPE_DMA_INDEX,
> >
> > It fixes the issue for me. Thanks.
>
> The count is actually the count, not count - 1. The real fix seems to
> be that r6xx requires 2 dw aligned transfers. The attached patch
> fixes the issue for me.
Yes, this one also works for me. Thanks.
--
Markus
next prev parent reply other threads:[~2013-01-03 8:33 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-22 20:35 radeon 0000:02:00.0: GPU lockup CP stall for more than 10000msec Borislav Petkov
2012-12-23 0:01 ` Alex Deucher
2012-12-23 0:25 ` Borislav Petkov
2012-12-23 0:25 ` Borislav Petkov
2012-12-23 0:42 ` Alex Deucher
2012-12-23 10:55 ` Borislav Petkov
2012-12-23 10:55 ` Borislav Petkov
2012-12-23 11:01 ` Andy Furniss
2012-12-23 11:07 ` Borislav Petkov
2012-12-23 11:19 ` Andy Furniss
2012-12-23 11:31 ` Borislav Petkov
2012-12-23 11:51 ` Markus Trippelsdorf
2012-12-23 12:22 ` Borislav Petkov
2012-12-23 13:31 ` Borislav Petkov
2012-12-25 4:50 ` Shuah Khan
2012-12-25 10:54 ` Borislav Petkov
2013-01-02 1:42 ` Antti Palosaari
2013-01-02 12:02 ` Borislav Petkov
2013-01-02 17:19 ` Jerome Glisse
2013-01-02 17:58 ` Antti Palosaari
2013-01-02 22:31 ` Jerome Glisse
2013-01-02 22:38 ` Markus Trippelsdorf
2013-01-02 23:37 ` Alex Deucher
2013-01-02 23:58 ` Shuah Khan
2013-01-02 23:59 ` Alex Deucher
2013-01-03 1:03 ` Antti Palosaari
2013-01-03 1:03 ` Antti Palosaari
2013-01-03 1:05 ` Shuah Khan
2013-01-03 8:33 ` Markus Trippelsdorf [this message]
2013-01-03 11:37 ` Boszormenyi Zoltan
2013-01-03 14:12 ` Deucher, Alexander
2013-01-03 15:30 ` Shuah Khan
2013-01-04 7:40 ` Borislav Petkov
2013-01-04 11:16 ` Boszormenyi Zoltan
2013-01-04 14:06 ` Alex Deucher
2012-12-23 11:52 ` Joe Perches
-- strict thread matches above, loose matches on Subject: below --
2013-01-10 9:38 Borislav Petkov
2013-01-10 16:21 ` Alex Deucher
2013-01-10 20:32 ` Borislav Petkov
2013-01-10 20:47 ` Alex Deucher
2013-01-11 11:43 ` Borislav Petkov
2013-01-15 12:19 ` Borislav Petkov
2013-01-15 14:04 ` Alex Deucher
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=20130103083322.GA230@x4 \
--to=markus@trippelsdorf.de \
--cc=alexander.deucher@amd.com \
--cc=alexdeucher@gmail.com \
--cc=andyqos@ukfsn.org \
--cc=bp@alien8.de \
--cc=crope@iki.fi \
--cc=dri-devel@lists.freedesktop.org \
--cc=j.glisse@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shuahkhan@gmail.com \
/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.