All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 105251] [Vega10]  GPU lockup on boot: VMC page fault
Date: Wed, 22 Aug 2018 20:21:43 +0000	[thread overview]
Message-ID: <bug-105251-502-5qPmNfq3ZF@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-105251-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1818 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=105251

--- Comment #23 from Andrey Grodzovsky <andrey.grodzovsky@amd.com> ---
(In reply to CheatCodesOfLife from comment #22)
> You're welcome.
> 
> Not the exact same problem, no. I can get a hard-lock by trying to use
> amdvlk to play rpcs3, but it doesn't produce the same error and it's not as
> consistent (takes up to 15 minutes to crash)
> 
> Not sure if it's worth noting but I went back and tried every Cemu version
> back to 1.5 and a lot of wine versions going back to 2.8. It happens every
> time as soon as the game loads.

Let's try to get some debug info for the VMC page fault then -  

Clone and build our open source register analyzer from here -
https://cgit.freedesktop.org/amd/umr/ 
Install trace-cmd utility 
Load driver with cmd line parameter amdgpu.vm_fault_stop=2 from grub
P.S Best to use latest kernel from here -
https://cgit.freedesktop.org/~agd5f/linux/log/?h=amd-staging-drm-next

After desktop is loaded type 

sudo trace-cmd start -e dma_fence -e gpu_scheduler -e amdgpu -v -e
"amdgpu:amdgpu_mm_rreg" -e "amdgpu:amdgpu_mm_wreg" -e "amdgpu:amdgpu_iv"
to enable kernel event tracing log

If possible to launch the game from shell then prepend the command with 
GALLIUM_DDEBUG=always 
to dump all the MESA commands into files in ~/ddebug_dumps/


Start the game. When the problem happens do the following - 

as root 
cd /sys/kernel/debug/tracing && cat trace > event_dump

as normal user or root
sudo umr -lb > umr_dump
sudo umr -O verbose,use_colour -R gfx[.] >> umr_dump
sudo umr -O halt_waves,use_colour -wa >> umr_dump
dmesg > dmesg_dump

Upload a tar/zip of all those files + all the files from ~/ddebug_dumps/

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2892 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2018-08-22 20:21 UTC|newest]

Thread overview: 81+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-26  9:39 [Bug 105251] [Vega10] GPU lockup on boot: VMC page fault bugzilla-daemon
2018-04-28  6:10 ` bugzilla-daemon
2018-04-29 13:29 ` bugzilla-daemon
2018-04-29 13:54 ` bugzilla-daemon
2018-05-24  5:24 ` bugzilla-daemon
2018-05-25 14:22 ` bugzilla-daemon
2018-06-01 17:31 ` bugzilla-daemon
2018-06-04 14:00 ` bugzilla-daemon
2018-06-04 17:52 ` bugzilla-daemon
2018-06-04 18:39 ` bugzilla-daemon
2018-06-05  8:50 ` bugzilla-daemon
2018-07-15 22:44 ` bugzilla-daemon
2018-07-15 22:56 ` bugzilla-daemon
2018-07-15 23:09 ` bugzilla-daemon
2018-07-16 15:13 ` bugzilla-daemon
2018-08-08 23:40 ` bugzilla-daemon
2018-08-14 19:19 ` bugzilla-daemon
2018-08-20  6:30 ` bugzilla-daemon
2018-08-20 15:13 ` bugzilla-daemon
2018-08-21  8:46 ` bugzilla-daemon
2018-08-21  8:48 ` bugzilla-daemon
2018-08-21 14:56 ` bugzilla-daemon
2018-08-21 15:12 ` bugzilla-daemon
2018-08-22 20:21 ` bugzilla-daemon [this message]
2018-08-24 14:11 ` bugzilla-daemon
2018-08-24 14:12 ` bugzilla-daemon
2018-08-24 14:24 ` bugzilla-daemon
2018-08-24 16:39 ` bugzilla-daemon
2018-08-24 19:35 ` bugzilla-daemon
2018-08-24 19:37 ` bugzilla-daemon
2018-08-25  2:48 ` bugzilla-daemon
2018-08-25  2:49 ` bugzilla-daemon
2018-08-25  5:59 ` bugzilla-daemon
2018-08-25  9:09 ` bugzilla-daemon
2018-08-27 16:12 ` bugzilla-daemon
2018-08-27 17:19 ` bugzilla-daemon
2018-08-27 23:14 ` bugzilla-daemon
2018-08-28 19:10 ` bugzilla-daemon
2018-08-28 19:20 ` bugzilla-daemon
2018-08-29  9:30 ` bugzilla-daemon
2018-08-29 14:32 ` bugzilla-daemon
2018-08-29 22:54 ` bugzilla-daemon
2018-08-30  1:37 ` bugzilla-daemon
2018-08-30  2:03 ` bugzilla-daemon
2018-08-30  2:41 ` bugzilla-daemon
2018-08-30 14:27 ` bugzilla-daemon
2018-08-30 14:33 ` bugzilla-daemon
2018-08-31 19:13 ` bugzilla-daemon
2018-09-03 13:26 ` bugzilla-daemon
2018-09-04 17:40 ` bugzilla-daemon
2018-09-06  4:07 ` bugzilla-daemon
2018-09-06  9:55 ` bugzilla-daemon
2018-09-11  8:36 ` bugzilla-daemon
2018-09-11 10:01 ` bugzilla-daemon
2018-09-12  3:26 ` bugzilla-daemon
2018-10-24  4:01 ` bugzilla-daemon
2018-10-24  8:38 ` bugzilla-daemon
2018-10-28 12:14 ` bugzilla-daemon
2018-10-28 23:19 ` bugzilla-daemon
2018-11-17 22:57 ` bugzilla-daemon
2018-11-18  1:13 ` bugzilla-daemon
2018-12-13  0:46 ` bugzilla-daemon
2018-12-13  9:05 ` bugzilla-daemon
2018-12-18  1:56 ` bugzilla-daemon
2018-12-18  2:08 ` bugzilla-daemon
2019-02-19  1:47 ` bugzilla-daemon
2019-05-19  2:38 ` bugzilla-daemon
2019-05-21 14:01 ` bugzilla-daemon
2019-05-21 14:02 ` bugzilla-daemon
2019-07-03 11:08 ` bugzilla-daemon
2019-07-04 15:19 ` bugzilla-daemon
2019-07-20 17:05 ` bugzilla-daemon
2019-07-22  7:40 ` bugzilla-daemon
2019-07-22  8:29 ` bugzilla-daemon
2019-07-22 20:15 ` bugzilla-daemon
2019-07-22 20:56 ` bugzilla-daemon
2019-07-22 20:57 ` bugzilla-daemon
2019-07-22 21:03 ` bugzilla-daemon
2019-07-22 21:06 ` bugzilla-daemon
2019-07-26 18:52 ` bugzilla-daemon
2019-11-19  8:31 ` bugzilla-daemon

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=bug-105251-502-5qPmNfq3ZF@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.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 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.