Comment # 15
on bug 91790
from Andy Furniss
(In reply to Andy Furniss from comment #13) > (In reply to Mathias Tillman from comment #11) > > (In reply to Alex Deucher from comment #10) > > > Created attachment 118056 [details] [review] [review] [review] [review] > > > possible fix > > > > > > I think this patch should fix it. > > > > No luck here I'm afraid - I'm having a hard time reproducing it during > > normal desktop usage (with or without the patch), but it did lockup while > > running Unigine Valley. > > I see drm-next-4.3 is now ahead again, haven't tested that yet. > > With patch + drm-next-4.3-wip, I haven't yet managed to lock valley - but > I've only had time to do a couple of runs (45 min then 90 min) from a clean > boot. Maybe later when I've been up a while doing other things I'll try > harder. > > Patch doesn't apply with git apply - did it by hand. I managed to lock it, seems that doing "something" between runs changes things, or first runs are lucky. FWIW I tried running Unreal 4.5 ElementalDemo after my long runs and I got a signal 7. After I later locked/hung valley I rebooted and tried again elemental from a clean boot and it ran OK, but after quitting. it now gives signal 7 again if I try to start it.
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
