[Bug 93652] Random crashes/freezing with amdgpu Fury X mesa 11.1

[bugzilla-daemon at bugs.freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=93652

Sebastian Jensen <s at gonx.dk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |s at gonx.dk

--- Comment #8 from Sebastian Jensen <s at gonx.dk> ---
Created attachment 123608
  --> https://bugs.freedesktop.org/attachment.cgi?id=123608&action=edit
Xorg blocked backtrace

Is there anything we can do to help debug this? The crashes still exist at
drm-next commit bafb86f5bc3173479002555dea7f31d943b12332 (May 9 13:49:56 +1000)
- basically 4.6.0-rc7.
The backtrace remains similar to what was posted earlier.

--- Comment #9 from odh0 <odh0 at gmx.net> ---
One of these commits fixes the issue for me but i don't know which one it is
exactly.


drm/amdgpu: make sure vertical front porch is at least 1
https://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm-fixes-4.6&id=0126d4b9a516256f2432ca0dc78ab293a8255378

drm/radeon: make sure vertical front porch is at least 1
https://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm-fixes-4.6&id=3104b8128d4d646a574ed9d5b17c7d10752cd70b

drm/amdgpu: set metadata pointer to NULL after freeing.
https://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm-fixes-4.6&id=0092d3edcb23fcdb8cbe4159ba94a534290ff982

I think it is 
drm/amdgpu: set metadata pointer to NULL after freeing.

This patch is not merged into drm-next 4.6 yet.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160510/a5ee2fbc/attachment-0001.html>