From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 200387] New: amdgpu uses unusually high memory
Date: Sun, 01 Jul 2018 15:54:10 +0000 [thread overview]
Message-ID: <bug-200387-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=200387
Bug ID: 200387
Summary: amdgpu uses unusually high memory
Product: Drivers
Version: 2.5
Kernel Version: 4.16.18, 4.17.3, 4.18.0-rc2
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: felix@feldspaten.org
Regression: No
Created attachment 277107
--> https://bugzilla.kernel.org/attachment.cgi?id=277107&action=edit
Config file for 4.17.3.
Hi there,
I'm experiencing some out-of-memory issues while running Cities:Skylines using
the amdgpu driver. Trying to run a new game cases a complete system-freeze
running any Kernel that runs the amdgpu driver instead of a rather old Kernel
using the amdgpu-pro driver. The memory is the system related main memory, not
the GPU memory.
System details:
I'm running Ubuntu Mate 16.04 with a custom build 4.17.3 Kernel (Find config
attached)
AMD FX-8350
32 GB RAM
Radeon RX470
Sample Main Memory usage.
Kernel 4.4 with amdgpu-pro driver - RAM Usage after 1 Minute: 2.4 GB
Kernel 4.17.3 with amdgpu driver - RAM Usage after 1 Minute: 13 GB
Kernel 4.16.18 with amdgpu driver - RAM Usage after 1 Minute: 13 GB
Kernel 4.18.0-rc2 with amdgpu driver - RAM Usage after 1 Minute: 13 GB
I get similar results with running Stardew Valley (Factor two difference,
clearly measurable)
Find attached the config file for the 4.17.3 Kernel. Other kernels have been
build using this config file and the default suggestions for any unconfigured
parameter.
Greetings,
Felix
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2018-07-01 15:54 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-01 15:54 bugzilla-daemon [this message]
2018-07-02 3:34 ` [Bug 200387] amdgpu uses unusually high memory bugzilla-daemon
2018-07-02 10:13 ` bugzilla-daemon
2018-07-02 10:55 ` bugzilla-daemon
2018-07-02 15:14 ` bugzilla-daemon
2018-07-02 15:14 ` bugzilla-daemon
2018-07-02 15:15 ` bugzilla-daemon
2018-07-02 15:15 ` bugzilla-daemon
2018-07-02 15:19 ` bugzilla-daemon
2018-07-02 15:19 ` bugzilla-daemon
2018-07-02 15:21 ` bugzilla-daemon
2018-07-02 15:39 ` bugzilla-daemon
2018-07-02 16:03 ` bugzilla-daemon
2018-07-02 16:29 ` bugzilla-daemon
2018-07-02 16:50 ` bugzilla-daemon
2018-07-02 20:40 ` bugzilla-daemon
2018-07-03 7:27 ` bugzilla-daemon
2018-07-03 7:42 ` bugzilla-daemon
2018-07-03 7:54 ` bugzilla-daemon
2018-07-03 7:55 ` bugzilla-daemon
2018-07-03 8:08 ` bugzilla-daemon
2018-07-03 8:11 ` bugzilla-daemon
2018-07-03 16:31 ` bugzilla-daemon
2018-07-03 16:45 ` bugzilla-daemon
2018-07-03 17:40 ` bugzilla-daemon
2018-07-03 19:16 ` bugzilla-daemon
2018-07-04 8:01 ` bugzilla-daemon
2018-07-04 8:40 ` bugzilla-daemon
2018-07-04 10:00 ` bugzilla-daemon
2018-07-05 17:09 ` bugzilla-daemon
2018-07-08 12:57 ` 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-200387-2300@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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.