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: Thu, 20 Dec 2018 16:20:33 +0000 [thread overview] Message-ID: <5a413fa2-c3a4-d603-2069-fd27b22062cc@amd.com> (raw) In-Reply-To: <CABXGCsORwHuOuFT273hTZSkC4tChUC_Mbj8gte2htTR2V0s79Q@mail.gmail.com> On 2018-12-20 11:07 a.m., Mikhail Gavrilov wrote: > On Thu, 20 Dec 2018 at 19:19, StDenis, Tom <Tom.StDenis@amd.com> wrote: >> >> Ya I was right. With a plain build I can access the files just fine. >> >> >> >> I did manage to get into a weird shell where I couldn't cat >> amdgpu_gca_config from bash though after a reboot (had updates pending) >> it works fine. >> >> If you can't cat those files then neither can umr. >> >> So NOTABUG :-) >> > > I am very happy for you. But what about me? > I don't have idea how make this files available on my system. > And of course I tried reboot and try again cat amdgpu_gca_config > several times but all times without success. Sorry I didn't mean to be dismissive. It's just not a bug in umr though. On Fedora I can access those files as root just fine: tom@fx8:~$ sudo bash [sudo] password for tom: root@fx8:/home/tom# cd /sys/kernel/debug/dri/0 root@fx8:/sys/kernel/debug/dri/0# xxd -e amdgpu_gca_config 00000000: 00000003 00000001 00000004 0000000b ................ 00000010: 00000001 00000002 00000004 00000100 ................ 00000020: 00000020 00000008 00000020 00000100 ....... ....... 00000030: 00000030 000004c0 00000000 00000003 0............... 00000040: 00000000 00000000 00000000 00000000 ................ 00000050: 00000000 00000000 24000042 00000002 ........B..$.... 00000060: 00000001 00004100 017f9fcf 0000008e .....A.......... 00000070: 00000001 000015dd 000000c6 0000d000 ................ 00000080: 00001458 X... root@fx8:/sys/kernel/debug/dri/0# There must be some sort of ACL or something going on here. Tom > > Also I note that not all files not permitted for read from > /sys/kernel/debug/dri/0/* > I was able to dump contents of some files in debugfs.txt (see attachments) > List of available for readind files: > amdgpu_evict_gtt > amdgpu_evict_vram > amdgpu_fence_info > amdgpu_firmware_info > amdgpu_gds_mm > amdgpu_gem_info > amdgpu_gpu_recover > amdgpu_gtt_mm > amdgpu_gws_mm > amdgpu_oa_mm > amdgpu_pm_info > amdgpu_sa_info > amdgpu_test_ib > amdgpu_vbios > amdgpu_vram_mm > clients > framebuffer > gem_names > internal_clients > name > state > ttm_page_pool > > May some kernel options restrict access for files in debugfs (for > example to amdgpu_gca_config)? > If yes on which options should I pay attention? > I have no more ideas. I tried everything. > > > > > -- > 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: Thu, 20 Dec 2018 16:20:33 +0000 [thread overview] Message-ID: <5a413fa2-c3a4-d603-2069-fd27b22062cc@amd.com> (raw) In-Reply-To: <CABXGCsORwHuOuFT273hTZSkC4tChUC_Mbj8gte2htTR2V0s79Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> On 2018-12-20 11:07 a.m., Mikhail Gavrilov wrote: > On Thu, 20 Dec 2018 at 19:19, StDenis, Tom <Tom.StDenis@amd.com> wrote: >> >> Ya I was right. With a plain build I can access the files just fine. >> >> >> >> I did manage to get into a weird shell where I couldn't cat >> amdgpu_gca_config from bash though after a reboot (had updates pending) >> it works fine. >> >> If you can't cat those files then neither can umr. >> >> So NOTABUG :-) >> > > I am very happy for you. But what about me? > I don't have idea how make this files available on my system. > And of course I tried reboot and try again cat amdgpu_gca_config > several times but all times without success. Sorry I didn't mean to be dismissive. It's just not a bug in umr though. On Fedora I can access those files as root just fine: tom@fx8:~$ sudo bash [sudo] password for tom: root@fx8:/home/tom# cd /sys/kernel/debug/dri/0 root@fx8:/sys/kernel/debug/dri/0# xxd -e amdgpu_gca_config 00000000: 00000003 00000001 00000004 0000000b ................ 00000010: 00000001 00000002 00000004 00000100 ................ 00000020: 00000020 00000008 00000020 00000100 ....... ....... 00000030: 00000030 000004c0 00000000 00000003 0............... 00000040: 00000000 00000000 00000000 00000000 ................ 00000050: 00000000 00000000 24000042 00000002 ........B..$.... 00000060: 00000001 00004100 017f9fcf 0000008e .....A.......... 00000070: 00000001 000015dd 000000c6 0000d000 ................ 00000080: 00001458 X... root@fx8:/sys/kernel/debug/dri/0# There must be some sort of ACL or something going on here. Tom > > Also I note that not all files not permitted for read from > /sys/kernel/debug/dri/0/* > I was able to dump contents of some files in debugfs.txt (see attachments) > List of available for readind files: > amdgpu_evict_gtt > amdgpu_evict_vram > amdgpu_fence_info > amdgpu_firmware_info > amdgpu_gds_mm > amdgpu_gem_info > amdgpu_gpu_recover > amdgpu_gtt_mm > amdgpu_gws_mm > amdgpu_oa_mm > amdgpu_pm_info > amdgpu_sa_info > amdgpu_test_ib > amdgpu_vbios > amdgpu_vram_mm > clients > framebuffer > gem_names > internal_clients > name > state > ttm_page_pool > > May some kernel options restrict access for files in debugfs (for > example to amdgpu_gca_config)? > If yes on which options should I pay attention? > I have no more ideas. I tried everything. > > > > > -- > 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-20 16:20 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 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 [this message] 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=5a413fa2-c3a4-d603-2069-fd27b22062cc@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.