<div dir="auto">Well, this patch shouldn't change behavior. Are you sure it's not some random thing? I know, for example, that SI isn't very stable with piglit on radeon either.<div dir="auto"><br></div><div dir="auto">Marek</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sep 1, 2017 12:28 PM, "Michel Dänzer" <<a href="mailto:michel@daenzer.net">michel@daenzer.net</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 01/09/17 07:23 PM, Nicolai Hähnle wrote:<br>
> On 01.09.2017 11:58, Michel Dänzer wrote:<br>
>> On 29/08/17 11:47 PM, Christian König wrote:<br>
>>> From: Marek Olšák <<a href="mailto:marek.olsak@amd.com">marek.olsak@amd.com</a>><br>
>>><br>
>>> For lower overhead in the CS ioctl.<br>
>>> Winsys allocators are not used with interprocess-sharable resources.<br>
>>><br>
>>> v2: It shouldn't crash anymore, but the kernel will reject the new flag.<br>
>>> v3 (christian): Rename the flag, avoid sending those buffers in the<br>
>>> BO list.<br>
>>> v4 (christian): Remove setting the kernel flag for now<br>
>><br>
>> This change seems to have caused a GPU hang when running piglit on my<br>
>> Kaveri with the radeon kernel driver. Haven't been able to isolate it to<br>
>> a specific test, seems to only happen when running multiple tests<br>
>> concurrently. There's a GPUVM fault before the hang, I suspect it's<br>
>> related:<br>
>><br>
>> radeon 0000:00:01.0: GPU fault detected: 146 0x0ae6760c<br>
>> radeon 0000:00:01.0: VM_CONTEXT1_PROTECTION_FAULT_<wbr>ADDR 0x000001D7<br>
>> radeon 0000:00:01.0: VM_CONTEXT1_PROTECTION_FAULT_<wbr>STATUS 0x0607600C<br>
>> VM fault (0x0c, vmid 3) at page 471, read from 'CPF' (0x43504600) (118)<br>
>><br>
>><br>
>> Any ideas?<br>
><br>
> Only that "read from CPF" means it can only be one of:<br>
><br>
> - command buffers<br>
> - indirect draw data<br>
> - predication data (conditional render)<br>
><br>
> (I hope I didn't miss anything)<br>
><br>
> Hmm, actually, I think CI has unavoidable VM faults related to<br>
> ARB_sparse_buffers, so this may be benign. You could try to exclude the<br>
> ARB_sparse_buffers tests.<br>
<br>
GL_ARB_sparse_buffer isn't supported with the radeon kernel driver AFAICT.<br>
<br>
<br>
--<br>
Earthling Michel Dänzer | <a href="http://www.amd.com" rel="noreferrer" target="_blank">http://www.amd.com</a><br>
Libre software enthusiast | Mesa and X developer<br>
</blockquote></div></div>