From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 92266] Unigine Valley hangs up on 4k resolution on R390X, while lower resolutions work
Date: Sat, 03 Oct 2015 13:13:59 +0000 [thread overview]
Message-ID: <bug-92266-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 768 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=92266
Bug ID: 92266
Summary: Unigine Valley hangs up on 4k resolution on R390X,
while lower resolutions work
Product: Mesa
Version: 11.0
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: mc.return@gmx.net
QA Contact: dri-devel@lists.freedesktop.org
The hangup occurs after a while, I never managed to finish a benchmark when
using 3840x2160 screen resolution.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2079 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:[~2015-10-03 13:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-03 13:13 bugzilla-daemon [this message]
2015-10-04 7:54 ` [Bug 92266] Unigine Valley hangs up on 4k resolution on R390X, while lower resolutions work bugzilla-daemon
2015-10-04 13:24 ` [Bug 92266] Unigine Valley hangs up on 3840x2160 and 2560x1600 resolutions " bugzilla-daemon
2015-10-05 21:04 ` [Bug 92266] Unigine Valley hangs up on 3840x2160 resolution " bugzilla-daemon
2015-10-05 21:09 ` bugzilla-daemon
2015-10-07 11:11 ` [Bug 92266] Unigine Valley benchmark hangs up in scene 9 with " bugzilla-daemon
2015-10-08 22:10 ` 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-92266-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.