From: "Grodzovsky, Andrey" <Andrey.Grodzovsky@amd.com> To: "Wentland, Harry" <Harry.Wentland@amd.com>, Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>, "Deucher, Alexander" <Alexander.Deucher@amd.com>, "Koenig, Christian" <Christian.Koenig@amd.com> Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>, "amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org> Subject: Re: After Vega 56/64 GPU hang I unable reboot system Date: Mon, 17 Dec 2018 19:08:28 +0000 [thread overview] Message-ID: <09781f6e-5ea3-ccfd-1aa2-79941b089863@amd.com> (raw) In-Reply-To: <3ffe451b-1f17-23a5-985b-28d26fbaf7da@amd.com> On 12/17/2018 01:51 PM, Wentland, Harry wrote: > On 2018-12-15 4:42 a.m., Mikhail Gavrilov wrote: >> On Sat, 15 Dec 2018 at 00:36, Wentland, Harry <Harry.Wentland@amd.com> wrote: >>> Looks like there's an error before this happens that might get us into this mess: >>> >>> [ 229.741741] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=28686, emitted seq=28688 >>> [ 229.741806] [drm] GPU recovery disabled. >>> >>> Harry >> Harry, Is this ever will be fixed? >> That annoying `ring gfx timeout` still follow me on all machines with >> Vega GPU more than year. >> Just yesterday I blocked the computer and went to sleep, at the >> morning I found out that I could not unlock the machine. >> After connected via ssh I saw again in the kernel log >> `[drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled >> seq=32778472, emitted seq=32778474` >> It means that this bug may happens even it I doing nothing on my machine. >> >> Should we wait for any improvement in localization this bug? >> Because I suppose message `[drm:amdgpu_job_timedout [amdgpu]] *ERROR* >> ring gfx timeout, signaled seq=32778472, emitted seq=32778474` not >> contain any useful info for fixing this bug. >> > I don't know much about ring gfx timeouts as my area of expertise revolves around the display side of things, not gfx. > > Alex, Christian, any ideas? > > Harry Please install UMR and dump gfx ring content and waves after the hang is happening. UMR at - https://cgit.freedesktop.org/amd/umr/ Waves dump sudo umr -O verbose,halt_waves -wa GFX ring dump sudo umr -O verbose,follow -R gfx[.] Andrey > >> Thanks. >> >> -- >> Best Regards, >> Mike Gavrilov. >> > _______________________________________________ > amd-gfx mailing list > amd-gfx@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/amd-gfx
WARNING: multiple messages have this Message-ID (diff)
From: "Grodzovsky, Andrey" <Andrey.Grodzovsky-5C7GfCeVMHo@public.gmane.org> To: "Wentland, Harry" <Harry.Wentland-5C7GfCeVMHo@public.gmane.org>, Mikhail Gavrilov <mikhail.v.gavrilov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>, "Deucher, Alexander" <Alexander.Deucher-5C7GfCeVMHo@public.gmane.org>, "Koenig, Christian" <Christian.Koenig-5C7GfCeVMHo@public.gmane.org> Cc: "linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org" <linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org>, "amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org" <amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org> Subject: Re: After Vega 56/64 GPU hang I unable reboot system Date: Mon, 17 Dec 2018 19:08:28 +0000 [thread overview] Message-ID: <09781f6e-5ea3-ccfd-1aa2-79941b089863@amd.com> (raw) In-Reply-To: <3ffe451b-1f17-23a5-985b-28d26fbaf7da-5C7GfCeVMHo@public.gmane.org> On 12/17/2018 01:51 PM, Wentland, Harry wrote: > On 2018-12-15 4:42 a.m., Mikhail Gavrilov wrote: >> On Sat, 15 Dec 2018 at 00:36, Wentland, Harry <Harry.Wentland@amd.com> wrote: >>> Looks like there's an error before this happens that might get us into this mess: >>> >>> [ 229.741741] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=28686, emitted seq=28688 >>> [ 229.741806] [drm] GPU recovery disabled. >>> >>> Harry >> Harry, Is this ever will be fixed? >> That annoying `ring gfx timeout` still follow me on all machines with >> Vega GPU more than year. >> Just yesterday I blocked the computer and went to sleep, at the >> morning I found out that I could not unlock the machine. >> After connected via ssh I saw again in the kernel log >> `[drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled >> seq=32778472, emitted seq=32778474` >> It means that this bug may happens even it I doing nothing on my machine. >> >> Should we wait for any improvement in localization this bug? >> Because I suppose message `[drm:amdgpu_job_timedout [amdgpu]] *ERROR* >> ring gfx timeout, signaled seq=32778472, emitted seq=32778474` not >> contain any useful info for fixing this bug. >> > I don't know much about ring gfx timeouts as my area of expertise revolves around the display side of things, not gfx. > > Alex, Christian, any ideas? > > Harry Please install UMR and dump gfx ring content and waves after the hang is happening. UMR at - https://cgit.freedesktop.org/amd/umr/ Waves dump sudo umr -O verbose,halt_waves -wa GFX ring dump sudo umr -O verbose,follow -R gfx[.] Andrey > >> Thanks. >> >> -- >> Best Regards, >> Mike Gavrilov. >> > _______________________________________________ > amd-gfx mailing list > amd-gfx@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/amd-gfx _______________________________________________ amd-gfx mailing list amd-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next prev parent reply other threads:[~2018-12-17 19:08 UTC|newest] Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-12-04 22:18 After Vega 56/64 GPU hang I unable reboot system Mikhail Gavrilov 2018-12-04 22:18 ` Mikhail Gavrilov 2018-12-14 19:36 ` Wentland, Harry 2018-12-14 19:36 ` Wentland, Harry 2018-12-15 9:42 ` Mikhail Gavrilov 2018-12-15 9:42 ` Mikhail Gavrilov 2018-12-17 18:51 ` Wentland, Harry 2018-12-17 18:51 ` Wentland, Harry 2018-12-17 19:08 ` Grodzovsky, Andrey [this message] 2018-12-17 19:08 ` Grodzovsky, Andrey 2018-12-19 18:35 ` Mikhail Gavrilov 2018-12-19 18:35 ` Mikhail Gavrilov 2018-12-19 20:21 ` Grodzovsky, Andrey 2018-12-19 20:21 ` Grodzovsky, Andrey 2018-12-19 20:51 ` StDenis, Tom 2018-12-19 20:51 ` StDenis, Tom 2018-12-19 20:56 ` StDenis, Tom 2018-12-19 20:56 ` StDenis, Tom 2018-12-19 21:14 ` Mikhail Gavrilov 2018-12-19 21:14 ` Mikhail Gavrilov 2018-12-19 21:21 ` Mikhail Gavrilov 2018-12-19 21:21 ` Mikhail Gavrilov 2018-12-19 22:41 ` StDenis, Tom 2018-12-19 22:41 ` StDenis, Tom 2018-12-20 3:29 ` Mikhail Gavrilov 2018-12-20 3:29 ` Mikhail Gavrilov 2018-12-20 11:17 ` StDenis, Tom 2018-12-20 11:17 ` StDenis, Tom 2018-12-20 11:45 ` Mikhail Gavrilov 2018-12-20 11:45 ` Mikhail Gavrilov 2018-12-20 14:06 ` StDenis, Tom 2018-12-20 14:06 ` StDenis, Tom 2018-12-20 14:08 ` StDenis, Tom 2018-12-20 14:08 ` StDenis, Tom 2018-12-20 14:19 ` 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-20 16:20 ` StDenis, Tom 2018-12-22 10:28 ` Mikhail Gavrilov 2018-12-22 10:28 ` Mikhail Gavrilov 2018-12-22 10:28 ` Mikhail Gavrilov 2019-01-03 20:23 ` 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-07 18:46 ` Grodzovsky, Andrey 2019-01-09 19:36 ` Mikhail Gavrilov 2019-01-09 19:36 ` Mikhail Gavrilov 2019-01-09 20:35 ` Grodzovsky, Andrey 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:12 ` Mikhail Gavrilov 2019-01-09 21:48 ` Grodzovsky, Andrey 2019-01-09 21:48 ` Grodzovsky, Andrey 2019-01-10 4:04 ` Mikhail Gavrilov 2019-01-10 4:04 ` Mikhail Gavrilov 2019-01-10 8:54 ` Michel Dänzer 2019-01-10 8:54 ` Michel Dänzer 2019-01-10 9:42 ` Mikhail Gavrilov 2019-01-10 9:42 ` Mikhail Gavrilov 2019-01-10 9:42 ` Mikhail Gavrilov 2019-01-10 10:38 ` Michel Dänzer 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:22 ` Mikhail Gavrilov 2019-01-10 15:31 ` StDenis, Tom 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=09781f6e-5ea3-ccfd-1aa2-79941b089863@amd.com \ --to=andrey.grodzovsky@amd.com \ --cc=Alexander.Deucher@amd.com \ --cc=Christian.Koenig@amd.com \ --cc=Harry.Wentland@amd.com \ --cc=amd-gfx@lists.freedesktop.org \ --cc=linux-mm@kvack.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: linkBe 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.