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 11:17:56 +0000 [thread overview]
Message-ID: <b3aba7f4-b131-64fe-88eb-c1e14e133c51@amd.com> (raw)
In-Reply-To: <CABXGCsMbP8W28NTx_y3viiN=3deiEVkLw0_HBFZa1Qt_8MUVjg@mail.gmail.com>
On 2018-12-19 10:29 p.m., Mikhail Gavrilov wrote:
> On Thu, 20 Dec 2018 at 03:41, StDenis, Tom <Tom.StDenis@amd.com> wrote:
>
>> 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
>>
>
> strace file is attached here.
Well yup the kernel is not letting you open the files:
openat(AT_FDCWD, "/sys/kernel/debug/dri/0/amdgpu_gca_config", O_RDONLY)
= -1 EPERM (Operation not permitted)
openat(AT_FDCWD, "/sys/kernel/debug/dri/0/amdgpu_regs", O_RDWR) = -1
EPERM (Operation not permitted)
openat(AT_FDCWD, "/sys/kernel/debug/dri/0/amdgpu_regs_didt", O_RDWR) =
-1 EPERM (Operation not permitted)
openat(AT_FDCWD, "/sys/kernel/debug/dri/0/amdgpu_regs_pcie", O_RDWR) =
-1 EPERM (Operation not permitted)
openat(AT_FDCWD, "/sys/kernel/debug/dri/0/amdgpu_regs_smc", O_RDWR) = -1
EPERM (Operation not permitted)
openat(AT_FDCWD, "/sys/kernel/debug/dri/0/amdgpu_sensors", O_RDWR) = -1
EPERM (Operation not permitted)
openat(AT_FDCWD, "/sys/kernel/debug/dri/0/amdgpu_wave", O_RDWR) = -1
EPERM (Operation not permitted)
openat(AT_FDCWD, "/sys/kernel/debug/dri/0/amdgpu_vram", O_RDWR) = -1
EPERM (Operation not permitted)
openat(AT_FDCWD, "/sys/kernel/debug/dri/0/amdgpu_gpr", O_RDWR) = -1
EPERM (Operation not permitted)
openat(AT_FDCWD, "/sys/kernel/debug/dri/0/amdgpu_iova", O_RDWR) = -1
ENOENT (No such file or directory)
openat(AT_FDCWD, "/sys/kernel/debug/dri/0/amdgpu_iomem", O_RDWR) = -1
EPERM (Operation not permitted)
openat(AT_FDCWD, "/sys/bus/pci/devices/0000:0b:00.0/vbios_version",
O_RDONLY) = 3
fstat(3, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
read(3, "xxx-xxx-xxx\n", 4096) = 12
close(3) = 0
openat(AT_FDCWD, "/sys/kernel/debug/dri/0/amdgpu_firmware_info",
O_RDONLY) = 3
fstat(3, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
read(3, "VCE feature version: 0, firmware"..., 4096) = 1059
read(3, "", 4096) = 0
close(3) = 0
openat(AT_FDCWD, "/sys/kernel/debug/dri/0/amdgpu_gca_config", O_RDONLY)
= -1 EPERM (Operation not permitted)
openat(AT_FDCWD, "/sys/kernel/debug/dri/0/amdgpu_ring_gfx", O_RDWR) = -1
EPERM (Operation not permitted)
As sudo/root you should be able to open these files with umr. What
happens if you just open a shell as root and run it?
Tom
next prev parent reply other threads:[~2018-12-20 11:18 UTC|newest]
Thread overview: 38+ 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-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 [this message]
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=b3aba7f4-b131-64fe-88eb-c1e14e133c51@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: 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