https://bugzilla.kernel.org/show_bug.cgi?id=94081
--- Comment #4 from Jan Vesely ---
This does not make sense, the work structure is zeroed so fence put should is
OK.
it looks like sometimes the lockup needs more than 1 GPU restart to manifest,
I'll replay without the good entries (at least it ex
https://bugzilla.kernel.org/show_bug.cgi?id=94081
--- Comment #3 from Jan Vesely ---
(In reply to Michel Dänzer from comment #2)
> Can you bisect?
It took a while (first bisect found unrelated i915 dispaly commit).
the failure was introduced in:
commit dd7cfd641228abb2669d8d047d5ec377b1835900
https://bugzilla.kernel.org/show_bug.cgi?id=94081
--- Comment #2 from Michel Dänzer ---
Can you bisect?
(In reply to Jan Vesely from comment #1)
> here's dmesg output for 3.17 kernel:
[...]
> [ 249.362280] [drm:r600_ib_test] *ERROR* radeon: fence wait failed (-35).
> [ 249.362281] [drm:rade
https://bugzilla.kernel.org/show_bug.cgi?id=94081
--- Comment #1 from Jan Vesely ---
here's dmesg output for 3.17 kernel:
(looks like ib test on ring 5 is missing in 3.18)
[ 249.015280] radeon :01:00.0: ring 0 stalled for more than 1msec
[ 249.015287] radeon :01:00.0: GPU lockup (w
