[Mesa-dev] [Bug 108524] [RADV] GPU lockup on event synchronization

2018-10-25 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=108524

Bas Nieuwenhuizen  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

--- Comment #2 from Bas Nieuwenhuizen  ---
Fixed with

commit d41c3cc01314fd2586ad2392a05647197d04c28d
Author: Bas Nieuwenhuizen 
Date:   Tue Oct 23 10:54:24 2018 +0200

radv: Emit enqueued pipeline barriers on event write.

Since the CPU can read them we need to execute any GPU->CPU
flushes before the event is written.

Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=108524
Fixes: f4e499ec791 "radv: add initial non-conformant radv vulkan driver"
Reviewed-by: Samuel Pitoiset 

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev


[Mesa-dev] [Bug 108524] [RADV] GPU lockup on event synchronization

2018-10-23 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=108524

--- Comment #1 from Bas Nieuwenhuizen  ---
I did not see a lockup* but this fixes the data issue:

https://patchwork.freedesktop.org/patch/257901/

*: I got some what looks like the program just trying to dump too much stuff
too the terminal, while the terminal cannot redraw because you are keeping a
commandbuffer in flight. You can avoid this by using the compute queue or by
dumping less stuff to the terminal (as fixing the data issue effectively does)

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev


[Mesa-dev] [Bug 108524] [RADV] GPU lockup on event synchronization

2018-10-23 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=108524

Bug ID: 108524
   Summary: [RADV]  GPU lockup on event synchronization
   Product: Mesa
   Version: 18.2
  Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
  Severity: normal
  Priority: medium
 Component: Drivers/Vulkan/radeon
  Assignee: mesa-dev@lists.freedesktop.org
  Reporter: nex...@gmail.com
QA Contact: mesa-dev@lists.freedesktop.org

I'm working on Device - Host - Device synchronization with VkEvent, but doing
that results to a lockup using radv. It works with amdvlk though as you can
read in the original issue on the Khronos github page here:
https://github.com/KhronosGroup/Vulkan-Docs/issues/755

Here is sample source code that reproduces the problem:
https://gist.github.com/neXyon/859b2e52bac9a5a56b804d8a9d5fa4a5

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev