All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrey Grodzovsky <Andrey.Grodzovsky@amd.com>
To: Christian Pernegger <pernegger@gmail.com>, amd-gfx@lists.freedesktop.org
Subject: Re: [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out or interrupted!
Date: Fri, 6 Dec 2019 10:45:35 -0500	[thread overview]
Message-ID: <08f54bf9-db69-ff9a-b3bb-477b2ac05eb0@amd.com> (raw)
In-Reply-To: <CAKbQEqEE3dgcF1bi-Sh5FQoHiU2TEHYn-H5fE92g6Pa+rgXbiQ@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2066 bytes --]

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@lists.freedesktop.org
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.freedesktop.org%2Fmailman%2Flistinfo%2Famd-gfx&amp;data=02%7C01%7Candrey.grodzovsky%40amd.com%7Cbb730551c8ef4057491908d779d90a9b%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637111845515070500&amp;sdata=RisL4HBqy35p25FOcp97EU%2F4Ldq6W1GJtkVANyzz8BY%3D&amp;reserved=0

[-- Attachment #1.2: Type: text/html, Size: 3175 bytes --]

[-- Attachment #2: Type: text/plain, Size: 153 bytes --]

_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

  parent reply	other threads:[~2019-12-06 15:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-05 23:14 [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out or interrupted! Christian Pernegger
2019-12-06  1:43 ` Liu, Zhan
2019-12-06 11:16   ` Christian Pernegger
2019-12-06 15:45 ` Andrey Grodzovsky [this message]
2019-12-07 10:35   ` Christian Pernegger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=08f54bf9-db69-ff9a-b3bb-477b2ac05eb0@amd.com \
    --to=andrey.grodzovsky@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=pernegger@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.