From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 84648] New: Lag/Pause When VRAM->GTT or GTT->VRAM transfer occur
Date: Sat, 04 Oct 2014 04:17:22 +0000 [thread overview]
Message-ID: <bug-84648-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1781 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=84648
Bug ID: 84648
Summary: Lag/Pause When VRAM->GTT or GTT->VRAM transfer occur
Product: Mesa
Version: git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: b747xx@gmail.com
Created attachment 107298
--> https://bugs.freedesktop.org/attachment.cgi?id=107298&action=edit
HUD showing FPS drop and mem transfer
I got an lag / pause (stopping for one to +- 5 seconds) when I get transfer of
memory from the VRAM to GTT and the opposite, the GTT to VRAM.
It append only on Minecraft (No problem with EVE-Online & Source Engine games),
even sometime when it is not on the screen, and in that case, the whole X ui
stay locked until the transfer finish. It usually go fine until the VRAM reach
between 280-300MB and it start playing with the GTT.
The bug Append with:
Kernel 3.17-rc2+ (did not test the RC1, 3.16 was fine)
Mesa GIT newer than somewhere in the beginning of september.
Note that these don't need to be recent for the two. A old kernel with a new
Mesa and a new Kernel with a old Mesa recreate the problem. Having the latest
GIT of the two don't fix the problem. (I did in fact update libdrm, llvm, mesa,
xf86.... after upgrading the kernel to rc2, thinking something changed and was
requiring a newer mesa.
I have attached a screenshot with the Gallium hud showing the FPS and memory.
PS : I thought initially that it was the same as BUG #82050 but got requested
to file another bug.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3362 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2014-10-04 4:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-04 4:17 bugzilla-daemon [this message]
2014-10-04 4:18 ` [Bug 84648] Lag/Pause When VRAM->GTT or GTT->VRAM transfer occur bugzilla-daemon
2014-10-06 9:13 ` bugzilla-daemon
2014-12-25 17:59 ` bugzilla-daemon
2015-01-28 20:50 ` bugzilla-daemon
2015-01-28 20:51 ` bugzilla-daemon
2015-02-02 22:02 ` bugzilla-daemon
2015-02-03 12:37 ` bugzilla-daemon
2015-02-06 2:34 ` bugzilla-daemon
2015-02-26 16:18 ` bugzilla-daemon
2015-03-14 17:11 ` bugzilla-daemon
2015-03-14 17:15 ` bugzilla-daemon
2015-03-14 17:19 ` bugzilla-daemon
2015-03-14 17:20 ` bugzilla-daemon
2015-03-14 17:39 ` bugzilla-daemon
2015-03-15 21:56 ` bugzilla-daemon
2015-05-01 21:56 ` 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-84648-502@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.