From: "StDenis, Tom" <Tom.StDenis@amd.com> To: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com> Cc: "Grodzovsky, Andrey" <Andrey.Grodzovsky@amd.com>, "Wentland, Harry" <Harry.Wentland@amd.com>, "Deucher, Alexander" <Alexander.Deucher@amd.com>, "Koenig, Christian" <Christian.Koenig@amd.com>, "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: Wed, 19 Dec 2018 22:41:03 +0000 [thread overview] Message-ID: <9b87556e-ed4d-6ec0-2f98-a08469b7f35e@amd.com> (raw) In-Reply-To: <CABXGCsMygWFqnkaZbpLEBd9aBkk9=-fRnDMNOnkRfPZaeheoCg@mail.gmail.com> On 2018-12-19 4:21 p.m., Mikhail Gavrilov wrote: > I see that backtrace in my previous message are borked. > I place backtrace in text file for more comfort reading in this message. The backtrace points to the segfault in umr caused when it fails to read the file. We want to know why it can't open the file. Something like sudo strace umr -R gfx[.] 2>&1 | tee strace.log will capture everything. In the mean time I can fix at least the segfault. The issue is why can't it open "amdgpu_ring_gfx". Tom > > > -- > Best Regards, > Mike Gavrilov. >
WARNING: multiple messages have this Message-ID (diff)
From: "StDenis, Tom" <Tom.StDenis-5C7GfCeVMHo@public.gmane.org> To: Mikhail Gavrilov <mikhail.v.gavrilov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> Cc: "Grodzovsky, Andrey" <Andrey.Grodzovsky-5C7GfCeVMHo@public.gmane.org>, "amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org" <amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>, "linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org" <linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org>, "Deucher, Alexander" <Alexander.Deucher-5C7GfCeVMHo@public.gmane.org>, "Wentland, Harry" <Harry.Wentland-5C7GfCeVMHo@public.gmane.org>, "Koenig, Christian" <Christian.Koenig-5C7GfCeVMHo@public.gmane.org> Subject: Re: After Vega 56/64 GPU hang I unable reboot system Date: Wed, 19 Dec 2018 22:41:03 +0000 [thread overview] Message-ID: <9b87556e-ed4d-6ec0-2f98-a08469b7f35e@amd.com> (raw) In-Reply-To: <CABXGCsMygWFqnkaZbpLEBd9aBkk9=-fRnDMNOnkRfPZaeheoCg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> On 2018-12-19 4:21 p.m., Mikhail Gavrilov wrote: > I see that backtrace in my previous message are borked. > I place backtrace in text file for more comfort reading in this message. The backtrace points to the segfault in umr caused when it fails to read the file. We want to know why it can't open the file. Something like sudo strace umr -R gfx[.] 2>&1 | tee strace.log will capture everything. In the mean time I can fix at least the segfault. The issue is why can't it open "amdgpu_ring_gfx". Tom > > > -- > Best Regards, > Mike Gavrilov. > _______________________________________________ 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-19 22:41 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 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 [this message] 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=9b87556e-ed4d-6ec0-2f98-a08469b7f35e@amd.com \ --to=tom.stdenis@amd.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=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.