From: Daniel Vetter <daniel@ffwll.ch>
To: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
Cc: Hillf Danton <hdanton@sina.com>,
dri-devel <dri-devel@lists.freedesktop.org>,
amd-gfx list <amd-gfx@lists.freedesktop.org>,
Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: gnome-shell stuck because of amdgpu driver [5.3 RC5]
Date: Tue, 3 Sep 2019 22:18:55 +0200 [thread overview]
Message-ID: <CAKMK7uH9q09XadTV5Ezm=9aODErD=w_+8feujviVnF5LO_fggA@mail.gmail.com> (raw)
In-Reply-To: <CABXGCsMG2YrybO4_5jHaFQQxy2ywB53pY63qRfXK=ZKx5qc2Bw@mail.gmail.com>
On Tue, Sep 3, 2019 at 8:07 PM Mikhail Gavrilov
<mikhail.v.gavrilov@gmail.com> wrote:
>
> On Tue, 3 Sep 2019 at 13:21, Hillf Danton <hdanton@sina.com> wrote:
> >
> > Describe the problems you are experiencing please.
> > Say is the screen locked up? Machine lockedup?
> > Anything unnormal after you see the warning?
> >
>
> According to my observations, all "gnome shell stuck warning" happened
> when me not sitting on the computer and the computer was locked.
>
> I did not notice any problems at the morning (I did not even look at
> the kernel logs), I found that the problem happened when I remotely
> connected to my computer via ssh from work and accidently look dmesg
> output.
>
> At the evening after work, I even played in the "Division", and still
> not noted any problems.
>
> 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? All the debuggin on the
dma_fence_wait side is just looking at the messenger, this isn't the
source of the problem.
-Daniel
>
> $ dmesg -T | grep gnome
>
> ---> I am goto sleep
> [Tue Sep 3 01:00:10 2019] gnome shell stuck warning
> [Tue Sep 3 01:00:55 2019] gnome shell stuck warning
> [Tue Sep 3 06:54:50 2019] gnome shell stuck warning
> <--- I am wake up at 8:00 am and sitting again on the computer
> ---> I am went to work at 9:30
> [Tue Sep 3 10:00:05 2019] gnome shell stuck warning
> [Tue Sep 3 10:10:01 2019] gnome shell stuck warning
> [Tue Sep 3 10:13:43 2019] gnome shell stuck warning
> [Tue Sep 3 10:23:37 2019] gnome shell stuck warning
> [Tue Sep 3 10:42:07 2019] gnome shell stuck warning
> [Tue Sep 3 10:42:57 2019] gnome shell stuck warning
> [Tue Sep 3 10:59:25 2019] gnome shell stuck warning
> [Tue Sep 3 11:08:35 2019] gnome shell stuck warning
> [Tue Sep 3 11:13:19 2019] gnome shell stuck warning
> [Tue Sep 3 11:15:20 2019] gnome shell stuck warning
> [Tue Sep 3 11:26:20 2019] gnome shell stuck warning
> [Tue Sep 3 11:26:20 2019] gnome shell stuck warning
> [Tue Sep 3 11:36:30 2019] gnome shell stuck warning
> [Tue Sep 3 11:46:08 2019] gnome shell stuck warning
> [Tue Sep 3 11:53:52 2019] gnome shell stuck warning
> [Tue Sep 3 11:56:36 2019] gnome shell stuck warning
> [Tue Sep 3 12:17:10 2019] gnome shell stuck warning
> [Tue Sep 3 12:20:20 2019] gnome shell stuck warning
> [Tue Sep 3 12:20:20 2019] gnome shell stuck warning
> [Tue Sep 3 12:30:46 2019] gnome shell stuck warning
> [Tue Sep 3 12:40:52 2019] gnome shell stuck warning
> [Tue Sep 3 12:55:30 2019] gnome shell stuck warning
> [Tue Sep 3 12:57:52 2019] gnome shell stuck warning
> [Tue Sep 3 13:04:00 2019] gnome shell stuck warning
> [Tue Sep 3 13:12:38 2019] gnome shell stuck warning
> [Tue Sep 3 13:14:32 2019] gnome shell stuck warning
> [Tue Sep 3 13:53:12 2019] gnome shell stuck warning
> [Tue Sep 3 14:12:52 2019] gnome shell stuck warning
> [Tue Sep 3 14:15:54 2019] gnome shell stuck warning
> [Tue Sep 3 14:17:04 2019] gnome shell stuck warning
> [Tue Sep 3 14:21:57 2019] gnome shell stuck warning
> [Tue Sep 3 14:22:10 2019] gnome shell stuck warning
> [Tue Sep 3 14:37:42 2019] gnome shell stuck warning
> [Tue Sep 3 14:41:51 2019] gnome shell stuck warning
> [Tue Sep 3 14:42:52 2019] gnome shell stuck warning
> [Tue Sep 3 14:46:35 2019] gnome shell stuck warning
> [Tue Sep 3 15:03:18 2019] gnome shell stuck warning
> [Tue Sep 3 15:16:50 2019] gnome shell stuck warning
> [Tue Sep 3 15:27:30 2019] gnome shell stuck warning
> [Tue Sep 3 15:27:41 2019] gnome shell stuck warning
> [Tue Sep 3 16:08:06 2019] gnome shell stuck warning
> [Tue Sep 3 16:24:16 2019] gnome shell stuck warning
> [Tue Sep 3 16:33:04 2019] gnome shell stuck warning
> [Tue Sep 3 16:52:10 2019] gnome shell stuck warning
> [Tue Sep 3 17:18:27 2019] gnome shell stuck warning
> [Tue Sep 3 17:25:30 2019] gnome shell stuck warning
> [Tue Sep 3 17:41:16 2019] gnome shell stuck warning
> [Tue Sep 3 17:43:32 2019] gnome shell stuck warning
> [Tue Sep 3 17:51:10 2019] gnome shell stuck warning
> [Tue Sep 3 18:41:44 2019] gnome shell stuck warning
> [Tue Sep 3 18:44:18 2019] gnome shell stuck warning
> [Tue Sep 3 19:03:07 2019] gnome shell stuck warning
> [Tue Sep 3 19:17:58 2019] gnome shell stuck warning
> <--- Returned to home and sitting again on the computer
>
> --
> Best Regards,
> Mike Gavrilov.
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2019-09-03 20:19 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 [this message]
[not found] ` <5d6f10a6.1c69fb81.6b104.af73SMTPIN_ADDED_MISSING@mx.google.com>
2019-09-04 8:37 ` Daniel Vetter
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='CAKMK7uH9q09XadTV5Ezm=9aODErD=w_+8feujviVnF5LO_fggA@mail.gmail.com' \
--to=daniel@ffwll.ch \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=hdanton@sina.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).