From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 97840] [regression] [tonga] Freeze since new memory manager enabled
Date: Sat, 17 Sep 2016 12:01:43 +0000 [thread overview]
Message-ID: <bug-97840-502-e9MQCGo0Qa@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-97840-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 2027 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=97840
--- Comment #3 from Mike Lothian <mike@fireburn.co.uk> ---
The amount of video memory on the card is being reported differently on the two
cards
- Device: AMD TONGA (DRM 3.6.0 / 4.8.0-rc1-agd5f+, LLVM 4.0.0) (0x6921)
+ Device: AMD TONGA (DRM 3.3.0 / 4.8.0-rc6-tip+, LLVM 4.0.0) (0x6921)
Version: 12.1.0
Accelerated: yes
- Video memory: 4062MB
+ Video memory: 4085MB
Unified memory: no
Preferred profile: core (0x1)
Max core profile version: 4.3
@@ -57,18 +57,18 @@
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.1
Memory info (GL_ATI_meminfo):
- VBO free memory - total: 4061 MB, largest block: 4061 MB
- VBO free aux. memory - total: 16047 MB, largest block: 16047 MB
- Texture free memory - total: 4061 MB, largest block: 4061 MB
- Texture free aux. memory - total: 16047 MB, largest block: 16047 MB
- Renderbuffer free memory - total: 4061 MB, largest block: 4061 MB
- Renderbuffer free aux. memory - total: 16047 MB, largest block: 16047 MB
+ VBO free memory - total: 4085 MB, largest block: 4085 MB
+ VBO free aux. memory - total: 4093 MB, largest block: 4093 MB
+ Texture free memory - total: 4085 MB, largest block: 4085 MB
+ Texture free aux. memory - total: 4093 MB, largest block: 4093 MB
+ Renderbuffer free memory - total: 4085 MB, largest block: 4085 MB
+ Renderbuffer free aux. memory - total: 4093 MB, largest block: 4093 MB
Memory info (GL_NVX_gpu_memory_info):
- Dedicated video memory: 4062 MB
- Total available memory: 20109 MB
- Currently available dedicated video memory: 4061 MB
+ Dedicated video memory: 4085 MB
+ Total available memory: 8178 MB
+ Currently available dedicated video memory: 4085 MB
Also it seems glxinfo was freezing printing this line:
GL_ARB_texture_cube_map_array, GL_ARB_texture_env_add,
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2846 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:[~2016-09-17 12:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-17 11:12 [Bug 97840] [regression] [tonga] Freeze since new memory manager enabled bugzilla-daemon
2016-09-17 11:12 ` bugzilla-daemon
2016-09-17 11:14 ` bugzilla-daemon
2016-09-17 12:01 ` bugzilla-daemon [this message]
2016-09-17 12:02 ` bugzilla-daemon
2016-09-20 3:41 ` bugzilla-daemon
2016-09-20 6:02 ` bugzilla-daemon
2016-09-20 6:04 ` bugzilla-daemon
2016-09-20 6:11 ` bugzilla-daemon
2016-09-20 17:51 ` bugzilla-daemon
2016-09-20 17:53 ` bugzilla-daemon
2016-09-20 17:55 ` bugzilla-daemon
2016-09-20 17:57 ` bugzilla-daemon
2016-09-21 2:07 ` bugzilla-daemon
2016-09-21 7:41 ` bugzilla-daemon
2016-11-03 13:12 ` 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-97840-502-e9MQCGo0Qa@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox