From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 101672] radeonsi: 3D engines causing frequent GPU lockups
Date: Wed, 26 Jul 2017 22:10:57 +0000 [thread overview]
Message-ID: <bug-101672-502-RtRLgKJOhm@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-101672-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1420 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=101672
--- Comment #10 from MirceaKitsune <sonichedgehog_hyperblast00@yahoo.com> ---
I was able to use parallel SSH sessions to monitor changes in the files
suggested by Max Staudt, which I did by using the command:
watch -n 1 cat filename
The relevant files that existed and I was able to watch are:
/sys/kernel/debug/dri/0/clients
/sys/kernel/debug/dri/0/gem_names
/sys/kernel/debug/dri/0/radeon_gtt_mm
/sys/kernel/debug/dri/0/radeon_vram_mm
/sys/kernel/debug/dri/0/ttm_dma_page_pool
/sys/kernel/debug/dri/0/ttm_page_pool
I will attach the captures of each output, each showing its file <= 1 second
before the freeze. I understand those files should retain information about
VRAM, which indicates whether this could be a progressive memory leak.
Very important note: It has taken me hours to obtain those outputs, and for a
while I thought the freeze was fixed by an update altogether. For over 2 hours
I was able to run all game engines that produced this crash without getting any
freeze whatsoever, which has never happened before! However the freeze returned
after I restarted my machine, meaning it's still present. I have no idea
whether there's a switch in my system that causes it to happen only sometimes,
but hopefully those files will say something.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2225 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
next prev parent reply other threads:[~2017-07-26 22:10 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-02 0:22 [Bug 101672] radeonsi: 3D engines causing frequent GPU lockups bugzilla-daemon
2017-07-02 0:23 ` bugzilla-daemon
2017-07-02 0:24 ` bugzilla-daemon
2017-07-02 0:24 ` bugzilla-daemon
2017-07-02 0:25 ` bugzilla-daemon
2017-07-02 0:25 ` bugzilla-daemon
2017-07-02 0:26 ` bugzilla-daemon
2017-07-02 15:24 ` bugzilla-daemon
2017-07-11 22:13 ` bugzilla-daemon
2017-07-24 11:59 ` bugzilla-daemon
2017-07-26 22:10 ` bugzilla-daemon [this message]
2017-07-26 22:11 ` bugzilla-daemon
2017-07-26 22:12 ` bugzilla-daemon
2017-07-26 22:12 ` bugzilla-daemon
2017-07-26 22:13 ` bugzilla-daemon
2017-07-26 22:13 ` bugzilla-daemon
2017-07-26 22:14 ` bugzilla-daemon
2017-07-26 22:39 ` bugzilla-daemon
2017-07-27 14:52 ` bugzilla-daemon
2017-07-29 13:31 ` bugzilla-daemon
2017-08-01 12:17 ` bugzilla-daemon
2017-08-04 12:33 ` bugzilla-daemon
2018-02-22 0:06 ` bugzilla-daemon
2018-02-22 0:07 ` bugzilla-daemon
2018-02-22 7:34 ` bugzilla-daemon
2018-02-26 21:28 ` bugzilla-daemon
2018-02-27 12:02 ` bugzilla-daemon
2018-03-09 21:39 ` bugzilla-daemon
2018-03-09 21:45 ` 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-101672-502-RtRLgKJOhm@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.