From: Daniel Vetter <daniel@ffwll.ch>
To: Hillf Danton <hdanton@sina.com>
Cc: Daniel Vetter <daniel@ffwll.ch>,
Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>,
dri-devel <dri-devel@lists.freedesktop.org>,
amd-gfx list <amd-gfx@lists.freedesktop.org>,
Linux kernel <linux-kernel@vger.kernel.org>,
Alex Deucher <alexdeucher@gmail.com>,
Harry Wentland <hwentlan@amd.com>
Subject: Re: gnome-shell stuck because of amdgpu driver [5.3 RC5]
Date: Wed, 4 Sep 2019 10:37:47 +0200 [thread overview]
Message-ID: <20190904083747.GE2112@phenom.ffwll.local> (raw)
In-Reply-To: <5d6f10a6.1c69fb81.6b104.af73SMTPIN_ADDED_MISSING@mx.google.com>
On Wed, Sep 04, 2019 at 09:17:16AM +0800, Hillf Danton wrote:
> Daniel Vetter <daniel@ffwll.ch>
> >>
> >> Now 11:01pm and "gnome shell stuck warning" not appear since 19:17. So
> >> looks like issue happens only when computer blocked and monitor in
> >> power save mode.
> >
> > I'd bet on runtime pm or some other power saving feature in amdgpu
> > shutting the interrupt handling down before we've handled all the
> > interrupts. That would then result in a stuck fence.
> >
> > Do we already know which fence is stuck?
>
> It is welcomed to shed a thread of light on how to collect/print that info.
> Say line:xxx-yyy in path/to/amdgpu/zzz.c
Extend your backtrac warning slightly like
WARN(r, "we're stuck on fence %pS\n", fence->ops);
Also adding Harry and Alex, I'm not really working on amdgpu ...
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
next prev parent reply other threads:[~2019-09-04 8:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190830032948.13516-1-hdanton@sina.com>
2019-09-03 6:48 ` gnome-shell stuck because of amdgpu driver [5.3 RC5] Mikhail Gavrilov
[not found] ` <5d6e2298.1c69fb81.b5532.8395SMTPIN_ADDED_MISSING@mx.google.com>
2019-09-03 18:07 ` Mikhail Gavrilov
2019-09-03 20:18 ` Daniel Vetter
[not found] ` <5d6f10a6.1c69fb81.6b104.af73SMTPIN_ADDED_MISSING@mx.google.com>
2019-09-04 8:37 ` Daniel Vetter [this message]
2019-09-04 22:26 ` Mikhail Gavrilov
2019-09-05 7:58 ` Daniel Vetter
2019-09-08 21:24 ` Mikhail Gavrilov
2019-09-09 9:15 ` Koenig, Christian
2019-09-15 19:47 ` Mikhail Gavrilov
[not found] <20190825141305.13984-1-hdanton@sina.com>
2019-08-26 9:24 ` Daniel Vetter
2019-08-29 22:03 ` mikhail.v.gavrilov
2019-08-25 11:27 Mikhail Gavrilov
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=20190904083747.GE2112@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=alexdeucher@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=hdanton@sina.com \
--cc=hwentlan@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikhail.v.gavrilov@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).