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

Christian Pernegger pernegger at gmail.com
Sat Dec 7 10:35:56 UTC 2019

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 uneventful.

If & when it crashes, I'll get back to you.


Am Fr., 6. Dez. 2019 um 16:45 Uhr schrieb Andrey Grodzovsky
<Andrey.Grodzovsky at amd.com>:
> 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 computers has been crashing while gaming rather a lot
> lately, with kernel messages pointing to amdgpu. First line see
> subject, rest in the attached log.
> SSH still works, attempts to shutdown/reboot don't quite finish.
> Radeon VII in an Asus Pro WS X570-Ace. Ubuntu 18.04.3 HWE, mesa-aco.
> This one was with kernel 5.3.0-24-generic [hwe-edge], mesa
> 19.3.0+aco+git1575452833-3409c06e26d-1bionic1, vesa20_* from
> linux-firmware-20191022, running Ori and the Blind Forest: Definitive
> Edition via Proton/WINED3D11 under Steam Remote Play. I've had similar
> crashes sporadically even with 5.0 [plain hwe] and linux-firmware
> completely stock, and with native games (e.g. Crusader Kings II)
> running locally.
> It used to be maybe once every other week, though, that was tolerable,
> now Ori usually triggers it in under an hour. Turning off ACO via
> RADV_PERFTEST=llvm makes it worse (not bad enough to make it trigger
> quickly and reliably. though), going back to kernel 5.0 helps (as in
> an hour or two might go by without a crash, but the performance impact
> is severe).
> All very vague. Which is why this isn't pretending to be a bug report,
> just a "has anyone seen this?" kind of shout-out. If it's worthy of
> following up, I'd be happy to provide further info, just tell me what.
> Cheers,
> C.
> _______________________________________________
> amd-gfx mailing list
> amd-gfx at lists.freedesktop.org
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.freedesktop.org%2Fmailman%2Flistinfo%2Famd-gfx&data=02%7C01%7Candrey.grodzovsky%40amd.com%7Cbb730551c8ef4057491908d779d90a9b%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637111845515070500&sdata=RisL4HBqy35p25FOcp97EU%2F4Ldq6W1GJtkVANyzz8BY%3D&reserved=0

More information about the amd-gfx mailing list