From: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
To: "Michel Dänzer" <michel@daenzer.net>
Cc: "Grodzovsky, Andrey" <Andrey.Grodzovsky@amd.com>,
"Deucher, Alexander" <Alexander.Deucher@amd.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"Wentland, Harry" <Harry.Wentland@amd.com>,
"Koenig, Christian" <Christian.Koenig@amd.com>,
"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>
Subject: Re: After Vega 56/64 GPU hang I unable reboot system
Date: Thu, 10 Jan 2019 14:42:14 +0500 [thread overview]
Message-ID: <CABXGCsMLZhOtDHpwL+U7=s7XHcDoRs3yauDBR81d0-j-Fo6f-g@mail.gmail.com> (raw)
Message-ID: <20190110094214.MiwnPKg2MTkTh4w3oByxHkzEjLmSozpdYPFGvFNb14Y@z> (raw)
In-Reply-To: <52b47c08-a173-fafc-2a56-ec3cf44db99b@daenzer.net>
On Thu, 10 Jan 2019 at 13:54, Michel Dänzer <michel@daenzer.net> wrote:
>
> Assuming that's using DXVK, it could be an issue between DXVK and RADV.
> I'd start by filing a bug report against RADV.
>
In the case of the last report, I agree it makes sense.
But from the beginning I started this discussion because "* ERROR *
ring gfx timeout" haunts me everywhere. For example I unable to unlock
computer after night. I connect via SSH and see in kernel log "* ERROR
* ring gfx timeout". Or another case I watching video on YouTube as
usual and some times computer are stuck. I again connect via SSH and
see in log "* ERROR * ring gfx timeout". So i am very tired from this
error and want really helps to fix it. But I suppose logs from dmesg
here is helpless. Then I asked the guys how to got really useful logs.
And Andrey was guide me how to do it with umr tool.
I am tried get logs with umr with well reproduced for me case.
So we are here.
--
Best Regards,
Mike Gavrilov.
next prev parent reply other threads:[~2019-01-10 9:42 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-04 22:18 Mikhail Gavrilov
2018-12-14 19:36 ` Wentland, Harry
2018-12-15 9:42 ` Mikhail Gavrilov
2018-12-17 18:51 ` Wentland, Harry
2018-12-17 19:08 ` Grodzovsky, Andrey
2018-12-19 18:35 ` Mikhail Gavrilov
2018-12-19 20:21 ` Grodzovsky, Andrey
2018-12-19 20:51 ` StDenis, Tom
2018-12-19 20:56 ` StDenis, Tom
2018-12-19 21:14 ` Mikhail Gavrilov
2018-12-19 21:21 ` Mikhail Gavrilov
2018-12-19 22:41 ` StDenis, Tom
2018-12-20 3:29 ` Mikhail Gavrilov
2018-12-20 11:17 ` StDenis, Tom
2018-12-20 11:45 ` Mikhail Gavrilov
2018-12-20 14:06 ` StDenis, Tom
2018-12-20 14:08 ` StDenis, Tom
2018-12-20 14:19 ` StDenis, Tom
[not found] ` <96c70496-ce62-b162-187c-ff34ebb84ec2-5C7GfCeVMHo@public.gmane.org>
2018-12-20 16:07 ` Mikhail Gavrilov
2018-12-20 16:20 ` StDenis, Tom
2018-12-22 10:28 ` Mikhail Gavrilov
2018-12-22 10:28 ` Mikhail Gavrilov
2019-01-03 20:23 ` Mikhail Gavrilov
2019-01-04 17:50 ` Mikhail Gavrilov
2019-01-07 18:46 ` Grodzovsky, Andrey
2019-01-09 19:36 ` Mikhail Gavrilov
2019-01-09 20:35 ` Grodzovsky, Andrey
2019-01-09 21:12 ` Mikhail Gavrilov
2019-01-09 21:12 ` Mikhail Gavrilov
2019-01-09 21:48 ` Grodzovsky, Andrey
2019-01-10 4:04 ` Mikhail Gavrilov
2019-01-10 8:54 ` Michel Dänzer
2019-01-10 9:42 ` Mikhail Gavrilov [this message]
2019-01-10 9:42 ` Mikhail Gavrilov
2019-01-10 10:38 ` Michel Dänzer
2019-01-10 15:22 ` Mikhail Gavrilov
2019-01-10 15:22 ` Mikhail Gavrilov
2019-01-10 15:31 ` StDenis, Tom
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='CABXGCsMLZhOtDHpwL+U7=s7XHcDoRs3yauDBR81d0-j-Fo6f-g@mail.gmail.com' \
--to=mikhail.v.gavrilov@gmail.com \
--cc=Alexander.Deucher@amd.com \
--cc=Andrey.Grodzovsky@amd.com \
--cc=Christian.Koenig@amd.com \
--cc=Harry.Wentland@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=linux-mm@kvack.org \
--cc=michel@daenzer.net \
/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