Re: [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out or interrupted!

2019-12-07 Thread Christian Pernegger
Sure. (I just hope it doesn't eat my data and/or unborn children. Sometimes I really wish one didn't need to switch out the whole kernel to get a different version of a bunch of components ...) Anyway, I have it (the new kernel) running since yesterday evening, the first Ori session, ~1.5 h, was

Re: [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out or interrupted!

2019-12-06 Thread Andrey Grodzovsky
The WARN stack trace after GPU reset kicks in points to not the latest code - can you please try running the same with kernel at the tip of https://cgit.freedesktop.org/~agd5f/linux/log/?h=amd-staging-drm-next ? Andrey On 12/5/19 6:14 PM, Christian Pernegger wrote: Hello, one of my

Re: [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out or interrupted!

2019-12-06 Thread Christian Pernegger
Am Fr., 6. Dez. 2019 um 02:43 Uhr schrieb Liu, Zhan : > I've seen a few people reported this issue on Freedesktop/Bugzilla. For > example: > https://bugs.freedesktop.org/show_bug.cgi?id=24. Yes, there's also https://bugs.freedesktop.org/show_bug.cgi?id=109955. To be honest, I couldn't say if

RE: [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out or interrupted!

2019-12-05 Thread Liu, Zhan
I've seen a few people reported this issue on Freedesktop/Bugzilla. For example: https://bugs.freedesktop.org/show_bug.cgi?id=24. They all experienced this issue while playing games. The higher GPU clock is, the more frequent issue can be reproduced. Also, some Reddit users pointed out all