From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 85454] New: Unigine Sanctuary with Wine crashes on Mesa Git
Date: Sat, 25 Oct 2014 20:06:33 +0000 [thread overview]
Message-ID: <bug-85454-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 985 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=85454
Bug ID: 85454
Summary: Unigine Sanctuary with Wine crashes on Mesa Git
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: commendsarnex@gmail.com
Created attachment 108416
--> https://bugs.freedesktop.org/attachment.cgi?id=108416&action=edit
backtrace
Hi guys,
When testing the Unigine Sanctuary windows benchmark, it crashes during the
inital loading screen with normal wined3d, with a crash in radeonsi.so. With
gallium nine, it works perfectly with no crashes.
I am using Mesa Git on a Radeon HD 7950. I can test any patches.
The backtrace is attached.
Thanks!
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2323 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-25 20:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-25 20:06 bugzilla-daemon [this message]
2014-10-27 7:43 ` [Bug 85454] Unigine Sanctuary with Wine crashes on Mesa Git bugzilla-daemon
2014-10-27 14:26 ` bugzilla-daemon
2014-10-27 14:27 ` bugzilla-daemon
2014-10-28 2:30 ` bugzilla-daemon
2014-10-28 3:12 ` bugzilla-daemon
2014-10-28 10:08 ` bugzilla-daemon
2014-10-28 14:53 ` bugzilla-daemon
2014-10-29 10:03 ` 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-85454-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.