From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 112304] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout causes system freeze
Date: Sun, 17 Nov 2019 06:12:48 +0000 [thread overview]
Message-ID: <bug-112304-502-YIIJrLRphY@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-112304-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1532 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=112304
--- Comment #7 from saadnaji89@gmail.com ---
Created attachment 145981
--> https://bugs.freedesktop.org/attachment.cgi?id=145981&action=edit
additional-journalctl-logs-during-game-play
I have enabled GPU reset with the following options
mdgpu.gpu_recovery=1 amdgpu.lockup_timeout=3000.
Then I have launch Counter Strike Source in attempts to capture logs as much as
I can before system freeze. I have added the new logs,
additional-journalctl-logs-during-game-play. Here is the snippet when error
begins from logs
Nov 17 01:02:36 archlinux kernel: amdgpu 0000:01:00.0: GPU fault detected: 146
0x066e480c
Nov 17 01:02:36 archlinux kernel: amdgpu 0000:01:00.0:
VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00100DB3
Nov 17 01:02:36 archlinux kernel: amdgpu 0000:01:00.0:
VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0E04800C
Nov 17 01:02:36 archlinux kernel: amdgpu 0000:01:00.0: VM fault (0x0c, vmid 7)
at page 1052083, read from '' (0x00000000) (72)
Nov 17 01:02:36 archlinux kernel: amdgpu 0000:01:00.0: GPU fault detected: 146
0x06ae880c
Nov 17 01:02:36 archlinux kernel: amdgpu 0000:01:00.0:
VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000
Nov 17 01:02:36 archlinux kernel: amdgpu 0000:01:00.0:
VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0F008010
Nov 17 01:02:36 archlinux kernel: amdgpu 0000:01:00.0: VM fault (0x10, vmid 7)
at page 0, write from '' (0x00000000) (8)
...
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2537 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-11-17 6:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-17 4:07 [Bug 112304] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout Causes System Freeze bugzilla-daemon
2019-11-17 4:08 ` bugzilla-daemon
2019-11-17 4:09 ` bugzilla-daemon
2019-11-17 4:09 ` bugzilla-daemon
2019-11-17 4:10 ` bugzilla-daemon
2019-11-17 4:14 ` [Bug 112304] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout causes system freeze bugzilla-daemon
2019-11-17 4:52 ` bugzilla-daemon
2019-11-17 5:11 ` bugzilla-daemon
2019-11-17 6:12 ` bugzilla-daemon [this message]
2019-11-17 6:34 ` bugzilla-daemon
2019-11-17 6:36 ` bugzilla-daemon
2019-11-17 6:37 ` bugzilla-daemon
2019-11-19 10:02 ` 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-112304-502-YIIJrLRphY@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.