Am 29.09.2016 22:34, schrieb Dieter Nützel:
[bisected]

gallium/radeon: add query fences and r600_get_hw_query_params

introduce regression on r600g/NI/Turks XT with Blender 2.76.
Picking/selecting with right mouse button result in SIG:

radeon: The kernel rejected CS, see dmesg for more information (-22).
radeon: The kernel rejected CS, see dmesg for more information (-22).
radeon: The kernel rejected CS, see dmesg for more information (-22).
radeon: The kernel rejected CS, see dmesg for more information (-22).
radeon: The kernel rejected CS, see dmesg for more information (-22).
radeon: The kernel rejected CS, see dmesg for more information (-22).
radeon: The kernel rejected CS, see dmesg for more information (-22).
radeon: The kernel rejected CS, see dmesg for more information (-22).
radeon: The kernel rejected CS, see dmesg for more information (-22).
Writing: /tmp/bh.crash.txt

[1]    Segmentation fault            blender

_This_ patch do _NOT_ solve it.

631c47384c1f45450359fd7d1df2c5f0c79f40bc is the first bad commit
commit 631c47384c1f45450359fd7d1df2c5f0c79f40bc
Author: Nicolai Hähnle <nicolai.haeh...@amd.com>
Date:   Wed Sep 14 10:38:33 2016 +0200

    gallium/radeon: add query fences and r600_get_hw_query_params

    We will support the waiting option in ARB_query_buffer_object using
WAIT_REG_MEM on an appropriate fence-like dword. Some queries conveniently write their results with the highest bit set, and we can just use that;
    for others, we have to write a fence explicitly.

ZPASS_DONE for occlusion queries writes its results with the high bit set, but it writes up to 8 pairs of results (one for each DB). We have to wait for all of these results, so let's just add an explicit fence.

The new function provides summary information to be used by subsequent
    patches.

    Reviewed-by: Edward O'Callaghan <funfunc...@folklore1984.net>
    Reviewed-by: Marek Olšák <marek.ol...@amd.com>

:040000 040000 bed7362ecccdebb63b505d50b3777dc10963aef9
fe9ca1f733c7897e1362194240e114482f91bbb3 M src

Regards,
Dieter.

Addendum (read the logs carefully...):

[25614.322361] [drm:radeon_cs_packet_next_reloc [radeon]] *ERROR* No packet3 for relocation for packet at 303.
[25614.322363] [drm] ib[303]=0xC0044700
[25614.322364] [drm] ib[304]=0x00000528
[25614.322364] [drm] ib[305]=0x00000080
[25614.322364] [drm] ib[306]=0x20000000
[25614.322365] [drm] ib[307]=0x80000000
[25614.322365] [drm] ib[308]=0x00000000
[25614.322384] [drm:evergreen_packet3_check.isra.14 [radeon]] *ERROR* bad EVENT_WRITE [25614.322399] [drm:radeon_cs_ioctl [radeon]] *ERROR* Invalid command stream ! [25614.322631] [drm:radeon_cs_packet_next_reloc [radeon]] *ERROR* No packet3 for relocation for packet at 717.
[25614.322636] [drm] ib[717]=0xC0044700
[25614.322636] [drm] ib[718]=0x00000528
[25614.322637] [drm] ib[719]=0x00000080
[25614.322637] [drm] ib[720]=0x20000000
[25614.322638] [drm] ib[721]=0x80000000
[25614.322638] [drm] ib[722]=0x00000000
[25614.322656] [drm:evergreen_packet3_check.isra.14 [radeon]] *ERROR* bad EVENT_WRITE [25614.322669] [drm:radeon_cs_ioctl [radeon]] *ERROR* Invalid command stream ! [25614.323004] [drm:radeon_cs_packet_next_reloc [radeon]] *ERROR* No packet3 for relocation for packet at 706.
[25614.323005] [drm] ib[706]=0xC0044700
[25614.323006] [drm] ib[707]=0x00000528
[25614.323006] [drm] ib[708]=0x00000080
[25614.323007] [drm] ib[709]=0x20000000
[25614.323007] [drm] ib[710]=0x80000000
[25614.323007] [drm] ib[711]=0x00000000
[25614.323025] [drm:evergreen_packet3_check.isra.14 [radeon]] *ERROR* bad EVENT_WRITE [25614.323039] [drm:radeon_cs_ioctl [radeon]] *ERROR* Invalid command stream !

Cheers,
Dieter.
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

Reply via email to