All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 102962] GPU crash running Overwatch in wine-staging
Date: Sun, 24 Sep 2017 22:51:06 +0000	[thread overview]
Message-ID: <bug-102962-502-Rb3jtzyEEY@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-102962-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1062 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=102962

--- Comment #2 from Tobias Auerochs <tobi291019@gmail.com> ---
As I mentioned, it causes a GPU crash, meaning the entire graphics session
freezes, other than mouse cursor, I'm not referring to wine simply crashing.

I'm not familiar with advanced OpenGL (specifically what wine requires to
implement d3d11) and if that would ever be allowed to cause a GPU crash at all
to begin with.

Also, to my knowledge (although I cannot test this myself currently), this does
not seem to happen on other drivers.

This either runs down to the sequence of OpenGL commands issued by wine
tripping mesa or wine not implementing d3d11 well enough and emitting invalid
OpenGL commands (which just happen to cause a GPU crash instead of a gl error
or process crash) to the best of my knowledge.

If you think this is better reported to wine directly, I can close this and
open a report there. (Sorry for the inconvenience then)

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1837 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

  parent reply	other threads:[~2017-09-24 22:51 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-24 15:05 [Bug 102962] GPU crash running Overwatch in wine-staging bugzilla-daemon
2017-09-24 22:11 ` bugzilla-daemon
2017-09-24 22:51 ` bugzilla-daemon [this message]
2017-10-21  4:40 ` bugzilla-daemon
2017-11-26 17:20 ` bugzilla-daemon
2017-11-27 12:33 ` bugzilla-daemon
2017-11-27 12:35 ` bugzilla-daemon
2017-12-06 21:49 ` bugzilla-daemon
2017-12-06 22:17 ` bugzilla-daemon
2018-03-31 17:36 ` bugzilla-daemon
2018-06-22 17:20 ` bugzilla-daemon
2018-07-18  7:18 ` bugzilla-daemon
2018-07-18 18:02 ` bugzilla-daemon
2018-09-08 10:03 ` bugzilla-daemon
2018-09-09 22:58 ` bugzilla-daemon
2018-09-10  3:36 ` bugzilla-daemon
2018-09-19 22:08 ` bugzilla-daemon
2019-09-25 18:00 ` 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-102962-502-Rb3jtzyEEY@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.