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:39:28 +0000 [thread overview]
Message-ID: <bug-101672-502-bqCyboeXpJ@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-101672-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1299 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=101672
--- Comment #17 from MirceaKitsune <sonichedgehog_hyperblast00@yahoo.com> ---
My understanding is limited when it comes to drivers and core OpenGL
components, so what I say might be completely irrelevant. Looking through the
logs, I'm noticing something suspicious in ttm_dma_page_pool:
pool refills pages freed inuse available name
wc 5008 0 3833 16199 radeon 0000:03:00.0
cached 22077 83375 4929 4 radeon 0000:03:00.0
The 'available' field of the 'cached' line says 4, which to me seems like a
very small value. radeon_gtt_mm and radeon_vram_mm also seem like they keep
adding more memory / pages / whatever than they are freeing, though this might
just be an impression. Others aren't raising any suspicion with me, but
hopefully someone more experienced can translate this data.
As a reminder, my video card has 2GB of memory while my system has 24 GB of RAM
and 8 GB of SWAP. Radeon R7 370 Gigabyte / Pitcairn Island / GCN 1.0 /
RadeonSI. As the amdgpu driver is not yet supported for my card, I'm still
running on the radeon driver (no fglrx).
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2101 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:39 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
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 [this message]
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-bqCyboeXpJ@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.