From: "Christian König" <deathsimple@vodafone.de>
To: "Marek Olšák" <maraeo@gmail.com>
Cc: dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: CIK hangs with kernel 3.15, bisected
Date: Wed, 28 May 2014 12:38:53 +0200 [thread overview]
Message-ID: <5385BCBD.7010803@vodafone.de> (raw)
In-Reply-To: <CAAxE2A6cV3M+MhWGnDKEJtDQ2FcqiX0Kp6vKu95OXx76JuFY9Q@mail.gmail.com>
I already tried a similar patch as well, without any more noticeable
crashes. But going to give this another round with your patch and openarena.
Thanks,
Christian.
Am 27.05.2014 23:55, schrieb Marek Olšák:
> Hi Christian,
>
> I test on Bonaire (ChipID = 0x665c). Unfortunately, the hangs are not
> fixed yet. They are very rare and very random. Therefore, I have come
> up with a patch which evicts page tables between IBs. See the
> attachment. With that patch applied, the system starts fine, compiz
> and glxgears work, but once I start playing openarena, it locks up
> pretty quickly.
>
> The patch shouldn't do anything in theory, because pages are moved
> back to VRAM immediately after that. However, the VRAM address of page
> tables may end up being different from before, which might be the root
> cause.
>
> Marek
>
> On Wed, May 14, 2014 at 2:11 PM, Christian König
> <deathsimple@vodafone.de> wrote:
>> Crap, any chance you can narrow it down a bit more?
>>
>> I've just tried a piglit quick test on my Bonaire and it seems to work
>> perfectly fine.
>>
>> What hw do you test on?
>>
>> Regards,
>> Christian.
>>
>> Am 13.05.2014 23:21, schrieb Marek Olšák:
>>
>>> Hi Christian,
>>>
>>> Even though some regressions are fixed by these patches:
>>>
>>> drm/radeon: fix page directory update size estimation
>>> drm/radeon: fix buffer placement under memory pressure v2
>>>
>>> and indeed, the texelFetch tests no longer hang, there is one more
>>> hang which needs to be fixed. :( All I know is the exact same commit
>>> causes it and it can only be reproduced by running whole piglit with
>>> concurrency enabled.
>>>
>>> My kernel git log:
>>>
>>> * 2ba22c8 - drm/radeon: fix buffer placement under memory pressure v2
>>> (10 hours ago) <Christian König>
>>> * 3af91e5 - drm/radeon: fix page directory update size estimation (21
>>> hours ago) <Christian König>
>>> * 6d2f294 - drm/radeon: use normal BOs for the page tables v4 (2
>>> months ago) <Christian König>
>>> * fa68834 - drm/radeon: further cleanup vm flushing & fencing (2
>>> months ago) <Christian König>
>>>
>>> fa68834 doesn't hang, but 2ba22c8 hangs, which means 6d2f294 or either
>>> of the two fixes is the first bad commit.
>>>
>>> Marek
>>>
>>> On Fri, May 9, 2014 at 8:03 PM, Marek Olšák <maraeo@gmail.com> wrote:
>>>> Hi Christian,
>>>>
>>>> This commit which first appeared in 3.15-rc1 causes hangs on Bonaire:
>>>>
>>>> commit 6d2f2944e95e504a7d33385eeeb9bb7fcca72592
>>>> Author: Christian König <christian.koenig@amd.com>
>>>> Date: Thu Feb 20 13:42:17 2014 +0100
>>>>
>>>> drm/radeon: use normal BOs for the page tables v4
>>>>
>>>> No need to make it more complicated than necessary,
>>>> just allocate the page tables as normal BO and
>>>> flush whenever the address change.
>>>>
>>>> v2: update comments and function name
>>>> v3: squash bug fixes, page directory and tables patch
>>>> v4: rebased on Mareks changes
>>>>
>>>> Signed-off-by: Christian König <christian.koenig@amd.com>
>>>>
>>>>
>>>> Reverting the commit gives me a lot of merge conflicts.
>>>>
>>>> The simplest way to reproduce the hangs is to run piglit with these
>>>> parameters:
>>>> -t texelFetch.fs
>>>>
>>>> Some of the tests allocate a lot of MSAA textures and the tests also
>>>> run in parallel, which creates a lot of memory pressure and probably
>>>> causes buffer evictions.
>>>>
>>>> Any idea what is wrong with it?
>>>>
>>>> Thanks,
>>>>
>>>> Marek
>>
next prev parent reply other threads:[~2014-05-28 10:39 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-09 18:03 CIK hangs with kernel 3.15, bisected Marek Olšák
2014-05-09 18:10 ` Rafał Miłecki
2014-05-09 21:39 ` Grigori Goronzy
2014-05-10 8:23 ` Christian König
2014-05-10 16:34 ` Christian König
2014-05-10 21:38 ` Marek Olšák
2014-05-11 9:06 ` Christian König
2014-05-12 12:50 ` Christian König
2014-05-12 23:38 ` Grigori Goronzy
2014-05-13 13:22 ` Alex Deucher
2014-05-13 13:57 ` Christian König
2014-05-13 15:19 ` Marek Olšák
2014-05-13 15:31 ` Christian König
2014-05-13 16:08 ` Marek Olšák
2014-05-13 19:50 ` Marek Olšák
2014-05-13 20:19 ` Grigori Goronzy
2014-05-13 20:27 ` Marek Olšák
2014-05-30 0:30 ` Grigori Goronzy
2014-05-30 11:30 ` Marek Olšák
2014-05-30 11:46 ` Grigori Goronzy
2014-05-30 11:51 ` Marek Olšák
2014-05-30 18:01 ` Grigori Goronzy
2014-05-13 21:21 ` Marek Olšák
2014-05-14 12:11 ` Christian König
2014-05-27 21:55 ` Marek Olšák
2014-05-28 10:38 ` Christian König [this message]
2014-05-29 16:30 ` Christian König
2014-05-29 16:51 ` Marek Olšák
2014-05-29 16:59 ` Christian König
2014-05-29 16:52 ` Alex Deucher
2014-05-30 15:57 ` Christian König
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=5385BCBD.7010803@vodafone.de \
--to=deathsimple@vodafone.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=maraeo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox