From: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
To: "Grodzovsky, Andrey" <Andrey.Grodzovsky@amd.com>
Cc: "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 23:35:54 +0500 [thread overview]
Message-ID: <CABXGCsPE36vkeycDQFhhsSQ0KhVxX4W=6Q5vt=hVzhZo3dZGWA@mail.gmail.com> (raw)
In-Reply-To: <09781f6e-5ea3-ccfd-1aa2-79941b089863@amd.com>
On Tue, 18 Dec 2018 at 00:08, Grodzovsky, Andrey
<Andrey.Grodzovsky@amd.com> wrote:
>
> 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 for respond.
What options should I specify in kernel command line?
On my setup `umr` terminated with message `Could not open ring debugfs
file` and crashes. But I am sure that debugfs enabled.
$ sudo umr -O verbose,halt_waves -wa
Cannot seek to MMIO address: Bad file descriptor
[ERROR]: Could not open ring debugfs fileSegmentation fault
# ls /sys/kernel/debug/dri/0/
amdgpu_dm_dtn_log amdgpu_ring_comp_1.1.0 amdgpu_vram_mm
amdgpu_evict_gtt amdgpu_ring_comp_1.1.1 amdgpu_wave
amdgpu_evict_vram amdgpu_ring_comp_1.2.0 clients
amdgpu_fence_info amdgpu_ring_comp_1.2.1 crtc-0
amdgpu_firmware_info amdgpu_ring_comp_1.3.0 crtc-1
amdgpu_gca_config amdgpu_ring_comp_1.3.1 crtc-2
amdgpu_gds_mm amdgpu_ring_gfx crtc-3
amdgpu_gem_info amdgpu_ring_kiq_2.1.0 crtc-4
amdgpu_gpr amdgpu_ring_sdma0 crtc-5
amdgpu_gpu_recover amdgpu_ring_sdma1 DP-1
amdgpu_gtt_mm 'amdgpu_ring_uvd<0>' DP-2
amdgpu_gws_mm 'amdgpu_ring_uvd_enc0<0>' DP-3
amdgpu_iomem 'amdgpu_ring_uvd_enc1<0>' framebuffer
amdgpu_oa_mm amdgpu_ring_vce0 gem_names
amdgpu_pm_info amdgpu_ring_vce1 HDMI-A-1
amdgpu_regs amdgpu_ring_vce2 HDMI-A-2
amdgpu_regs_didt amdgpu_sa_info HDMI-A-3
amdgpu_regs_pcie amdgpu_sensors internal_clients
amdgpu_regs_smc amdgpu_test_ib name
amdgpu_ring_comp_1.0.0 amdgpu_vbios state
amdgpu_ring_comp_1.0.1 amdgpu_vram ttm_page_pool
--
Best Regards,
Mike Gavrilov.
next prev parent reply other threads:[~2018-12-19 18:36 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 [this message]
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
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='CABXGCsPE36vkeycDQFhhsSQ0KhVxX4W=6Q5vt=hVzhZo3dZGWA@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 \
/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