From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 95329] Metro 2033 Redux benchmark fails to start
Date: Mon, 09 May 2016 19:28:42 +0000 [thread overview]
Message-ID: <bug-95329-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1629 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=95329
Bug ID: 95329
Summary: Metro 2033 Redux benchmark fails to start
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: 0xe2.0x9a.0x9b@gmail.com
QA Contact: dri-devel@lists.freedesktop.org
Mesa: 11.3.0-devel (git-57763ee)
GPU: R9 390 (dynamic power management: disabled)
Linux kernel: 4.5.0
Kernel module: radeon
Steps to reproduce the issue:
1) cd ".steam/root/steamapps/common/Metro 2033 Redux"
2) mv metro metro.bin
3) ln -s benchmark.sh metro
4) Edit benchmark.sh and replace "./metro" with "./metro.bin"
5) Copy the file "user.cfg" (attached to this bug report) to directory
"110000106d2b5d5"
6) Start the Steam client from command-line
7) Start Metro 2033 Redux from the Steam client
Segmentation fault (core dumped)
./metro.bin -benchmark benchmarks\\benchmark33 -bench_runs 1 -output_file
benchmark.log -close_on_finish
Notes:
- Running "gdb metro.bin core" does not provide useful information
- AMD drivers (fglrx) are working OK
- Step 5 is maybe optional, but I haven't verified this
Running "valgrind --tool=callgrind" for about an hour seems to indicate that
the issue may be linked to very slow shader compilation, but this is
inconclusive. AMD drivers (fglrx) start the benchmark much faster.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2992 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 reply other threads:[~2016-05-09 19:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-09 19:28 bugzilla-daemon [this message]
2016-05-09 19:29 ` [Bug 95329] Metro 2033 Redux benchmark fails to start bugzilla-daemon
2016-05-11 12:26 ` bugzilla-daemon
2016-05-17 12:03 ` bugzilla-daemon
2018-07-10 17:18 ` bugzilla-daemon
2018-07-10 23:11 ` 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-95329-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).