On 03.07.2014 04:31, Christian K?nig wrote:
>> FWIW, I've also had successful runs with the first three of the split
>> changes, and with all of them.
> Ok I've just pushed a branch testing-3.15-v3 to fdo which moves all page
> table allocation to the end of VRAM. Please try with this memory layout
Am 03.07.2014 05:48, schrieb Michel D?nzer:
> On 03.07.2014 04:31, Christian K?nig wrote:
>>> FWIW, I've also had successful runs with the first three of the split
>>> changes, and with all of them.
>> Ok I've just pushed a branch testing-3.15-v3 to fdo which moves all page
>> table allocation to t
> FWIW, I've also had successful runs with the first three of the split
> changes, and with all of them.
Ok I've just pushed a branch testing-3.15-v3 to fdo which moves all page
table allocation to the end of VRAM. Please try with this memory layout,
it should give us a good idea if it's indeed a
On 01.07.2014 21:16, Christian K?nig wrote:
> Am 01.07.2014 08:48, schrieb Michel D?nzer:
>> On 30.06.2014 16:43, Christian K?nig wrote:
>>> Am 30.06.2014 08:10, schrieb Michel D?nzer:
On 29.06.2014 19:34, Christian K?nig wrote:
> I've just pushed the branch testing-3.15 to
> git://peo
On 30.06.2014 16:43, Christian K?nig wrote:
> Am 30.06.2014 08:10, schrieb Michel D?nzer:
>> On 29.06.2014 19:34, Christian K?nig wrote:
>>> I've just pushed the branch testing-3.15 to
>>> git://people.freedesktop.org/~deathsimple/linux. It's based on 3.15.2
>>> and contains the "stop poisoning the
Am 01.07.2014 08:48, schrieb Michel D?nzer:
> On 30.06.2014 16:43, Christian K?nig wrote:
>> Am 30.06.2014 08:10, schrieb Michel D?nzer:
>>> On 29.06.2014 19:34, Christian K?nig wrote:
I've just pushed the branch testing-3.15 to
git://people.freedesktop.org/~deathsimple/linux. It's based
On 29.06.2014 19:34, Christian K?nig wrote:
>
> I've just pushed the branch testing-3.15 to
> git://people.freedesktop.org/~deathsimple/linux. It's based on 3.15.2
> and contains the "stop poisoning the GART TLB" patch backported to 3.15
> and a couple of things that I would like to try.
Running
Am 30.06.2014 08:10, schrieb Michel D?nzer:
> On 29.06.2014 19:34, Christian K?nig wrote:
>> I've just pushed the branch testing-3.15 to
>> git://people.freedesktop.org/~deathsimple/linux. It's based on 3.15.2
>> and contains the "stop poisoning the GART TLB" patch backported to 3.15
>> and a coupl
Am 27.06.2014 10:59, schrieb Michel D?nzer:
> On 27.06.2014 17:26, Christian K?nig wrote:
>> Am 27.06.2014 04:31, schrieb Michel D?nzer:
>>> On 25.06.2014 12:59, Michel D?nzer wrote:
With these patches, 3.15 just survived two piglit runs on my Bonaire,
one with the GART poisoning fix and
On 27.06.2014 17:26, Christian K?nig wrote:
> Am 27.06.2014 04:31, schrieb Michel D?nzer:
>> On 25.06.2014 12:59, Michel D?nzer wrote:
>>>
>>> With these patches, 3.15 just survived two piglit runs on my Bonaire,
>>> one with the GART poisoning fix and one without. It never survived a
>>> single r
On 25.06.2014 12:59, Michel D?nzer wrote:
> On 24.06.2014 19:14, Christian K?nig wrote:
>> Am 24.06.2014 08:49, schrieb Michel D?nzer:
>>> On 23.06.2014 18:56, Christian K?nig wrote:
Am 23.06.2014 10:15, schrieb Michel D?nzer:
> On 19.06.2014 18:45, Christian K?nig wrote:
>
>> I th
Am 27.06.2014 04:31, schrieb Michel D?nzer:
> On 25.06.2014 12:59, Michel D?nzer wrote:
>> On 24.06.2014 19:14, Christian K?nig wrote:
>>> Am 24.06.2014 08:49, schrieb Michel D?nzer:
On 23.06.2014 18:56, Christian K?nig wrote:
> Am 23.06.2014 10:15, schrieb Michel D?nzer:
>> On 19.06.2
Am 25.06.2014 05:59, schrieb Michel D?nzer:
> On 24.06.2014 19:14, Christian K?nig wrote:
>> Am 24.06.2014 08:49, schrieb Michel D?nzer:
>>> On 23.06.2014 18:56, Christian K?nig wrote:
Am 23.06.2014 10:15, schrieb Michel D?nzer:
> On 19.06.2014 18:45, Christian K?nig wrote:
>
>> I
On 24.06.2014 19:14, Christian K?nig wrote:
> Am 24.06.2014 08:49, schrieb Michel D?nzer:
>> On 23.06.2014 18:56, Christian K?nig wrote:
>>> Am 23.06.2014 10:15, schrieb Michel D?nzer:
On 19.06.2014 18:45, Christian K?nig wrote:
> I think even when we revert to the old code we have a
On 23.06.2014 18:56, Christian K?nig wrote:
> Am 23.06.2014 10:15, schrieb Michel D?nzer:
>> On 19.06.2014 18:45, Christian K?nig wrote:
>>
>>> I think even when we revert to the old code we have a couple of unsolved
>>> problems with the VM support or in the driver in general where we should
>>> t
Am 24.06.2014 08:49, schrieb Michel D?nzer:
> On 23.06.2014 18:56, Christian K?nig wrote:
>> Am 23.06.2014 10:15, schrieb Michel D?nzer:
>>> On 19.06.2014 18:45, Christian K?nig wrote:
>>>
I think even when we revert to the old code we have a couple of unsolved
problems with the VM suppor
On 19.06.2014 18:45, Christian K?nig wrote:
> Am 19.06.2014 03:48, schrieb Michel D?nzer:
>> On 15.06.2014 21:48, Christian K?nig wrote:
>>>
>>> No idea what goes wrong when Marek runs piglit, but 3.15.0+"stop
>>> poisoning the GART TLB"+"force_gtt" is rock solid here.
>> FWIW, 3.15 doesn't survive
Am 23.06.2014 10:15, schrieb Michel D?nzer:
> On 19.06.2014 18:45, Christian K?nig wrote:
>> Am 19.06.2014 03:48, schrieb Michel D?nzer:
>>> On 15.06.2014 21:48, Christian K?nig wrote:
No idea what goes wrong when Marek runs piglit, but 3.15.0+"stop
poisoning the GART TLB"+"force_gtt" is
On 19.06.2014 19:20, Marek Ol??k wrote:
> Hi Michel,
>
> 3.15 doesn't contain Christian's fix yet, so it should be always
> broken for everybody. The fix is currently only in 3.16.
>
> Alternatively, you can cherry-pick the fix to 3.15, but it doesn't
> apply cleanly.
That's a good point. Sorry,
Hi Marek,
> There is a workaround in 3.15 which disables sDMA and uses CP DMA for
> copying buffers. It seems to help Christian's machine, but not mine.
With stressing the box with piglit I was able to bring my machine down
with the CP DMA as well, only cherry-picking the "stop poisoning the
GAR
Hi Michel,
3.15 doesn't contain Christian's fix yet, so it should be always
broken for everybody. The fix is currently only in 3.16.
Alternatively, you can cherry-pick the fix to 3.15, but it doesn't
apply cleanly.
There is a workaround in 3.15 which disables sDMA and uses CP DMA for
copying buf
Am 19.06.2014 03:48, schrieb Michel D?nzer:
> On 15.06.2014 21:48, Christian K?nig wrote:
>> Am 13.06.2014 23:31, schrieb Alex Deucher:
>>> On Fri, Jun 13, 2014 at 11:45 AM, Christian K?nig
>>> wrote:
Hi Marek,
ah, yes! Piglit in combination with that patch can indeed crash the box.
On 15.06.2014 21:48, Christian K?nig wrote:
> Am 13.06.2014 23:31, schrieb Alex Deucher:
>> On Fri, Jun 13, 2014 at 11:45 AM, Christian K?nig
>> wrote:
>>> Hi Marek,
>>>
>>> ah, yes! Piglit in combination with that patch can indeed crash the box.
>>>
>>> Going to investigate now that I can reprodu
Am 13.06.2014 23:31, schrieb Alex Deucher:
> On Fri, Jun 13, 2014 at 11:45 AM, Christian K?nig
> wrote:
>> Hi Marek,
>>
>> ah, yes! Piglit in combination with that patch can indeed crash the box.
>>
>> Going to investigate now that I can reproduce it.
> I wonder if it's a clockgating issue with th
Hi Marek,
ah, yes! Piglit in combination with that patch can indeed crash the box.
Going to investigate now that I can reproduce it.
Thanks,
Christian.
Am 13.06.2014 15:19, schrieb Marek Ol??k:
> Hi,
>
> With my "force_gtt" patch, Cape Verde is unstable too, so all GCN
> chips are affected.
>
>
On Fri, Jun 13, 2014 at 11:45 AM, Christian K?nig
wrote:
> Hi Marek,
>
> ah, yes! Piglit in combination with that patch can indeed crash the box.
>
> Going to investigate now that I can reproduce it.
I wonder if it's a clockgating issue with the MC or BIF? You might
try adjusting the rdev->cg_fl
Hi,
With my "force_gtt" patch, Cape Verde is unstable too, so all GCN
chips are affected.
I recommend applying that patch, because it will reproduce the problem
faster. Without it, the hangs are very rare and it may take a while
before they occur.
Marek
On Thu, Jun 12, 2014 at 1:23 PM, Christia
Please do so, and you might want to try 3.15.0 as well.
I've tested multiple piglit runs over night with my Bonaire and 3.15.0
and that seemed to work perfectly fine.
Going to test Alex drm-next-3.16 a bit more as well.
Christian.
Am 11.06.2014 12:56, schrieb Marek Ol??k:
> I only tested Bonai
I only tested Bonaire. I can test Cape Verde if needed.
Marek
On Wed, Jun 11, 2014 at 11:29 AM, Christian K?nig
wrote:
> Crap, I already wanted to check back with you if that really fixes your
> problems.
>
> Thanks for the info, this crash also only happens on CIK doesn't it?
>
> Christian.
>
>
Crap, I already wanted to check back with you if that really fixes your
problems.
Thanks for the info, this crash also only happens on CIK doesn't it?
Christian.
Am 11.06.2014 01:30, schrieb Marek Ol??k:
> Sorry to tell you the bad news. This patch doesn't fix the hangs on my
> machine.
>
> I
Sorry to tell you the bad news. This patch doesn't fix the hangs on my machine.
I tested drm-next-3.16 from Alex's tree. I also switched copying from
SDMA to CP DMA, which hung too.
I also tried this:
git checkout (the problematic commit):
6d2f294 - drm/radeon: use normal BOs for the page tables
Am 04.06.2014 15:46, schrieb Alex Deucher:
> On Wed, Jun 4, 2014 at 9:29 AM, Christian K?nig
> wrote:
>> From: Christian K?nig
>>
>> When we set the valid bit on invalid GART entries they are
>> loaded into the TLB when an adjacent entry is loaded. This
>> poisons the TLB with invalid entries wh
From: Christian K?nig
When we set the valid bit on invalid GART entries they are
loaded into the TLB when an adjacent entry is loaded. This
poisons the TLB with invalid entries which are sometimes
not correctly removed on TLB flush.
For stable inclusion the patch probably needs to be modified a
On Wed, Jun 4, 2014 at 9:29 AM, Christian K?nig
wrote:
> From: Christian K?nig
>
> When we set the valid bit on invalid GART entries they are
> loaded into the TLB when an adjacent entry is loaded. This
> poisons the TLB with invalid entries which are sometimes
> not correctly removed on TLB flu
34 matches
Mail list logo