From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@bugs.freedesktop.org
Subject: [Bug 93652] Random crashes/freezing with amdgpu Fury X mesa 11.1
Date: Tue, 10 May 2016 20:16:03 +0000
Message-ID:
changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |s@gonx.dk
--- Comment #8 from Sebastian Jensen ---
Created attachment 123608
--> https://bugs.freedesktop.org/attachment.cgi?id=3D123608&action=3Dedit
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 +1=
000)
- basically 4.6.0-rc7.
The backtrace remains similar to what was posted earlier.
--- Comment #9 from odh0
What
Removed
Added
CC
s@gonx.dk
One of these commits fixes the issue for me but i don't know w=
hich one it is
exactly.
drm/amdgpu: make sure vertical front porch is at least 1
https://cgit.freedes=
ktop.org/~agd5f/linux/commit/?h=3Ddrm-fixes-4.6&id=3D0126d4b9a516256f24=
32ca0dc78ab293a8255378
drm/radeon: make sure vertical front porch is at least 1
https://cgit.freedes=
ktop.org/~agd5f/linux/commit/?h=3Ddrm-fixes-4.6&id=3D3104b8128d4d646a57=
4ed9d5b17c7d10752cd70b
drm/amdgpu: set metadata pointer to NULL after freeing.
https://cgit.freedes=
ktop.org/~agd5f/linux/commit/?h=3Ddrm-fixes-4.6&id=3D0092d3edcb23fcdb8c=
be4159ba94a534290ff982
I think it is=20
drm/amdgpu: set metadata pointer to NULL after freeing.
This patch is not merged into drm-next 4.6 yet.
Created attachment 123608=
[details]
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 +1=
000)
- basically 4.6.0-rc7.
The backtrace remains similar to what was posted earlier.