From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 93360] [radeonsi/llvm] Segfault in CS:GO
Date: Sun, 13 Dec 2015 20:32:07 +0000 [thread overview]
Message-ID: <bug-93360-502-tCOBz78i1M@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-93360-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 685 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=93360
--- Comment #5 from Tobias Droste <tdroste@gmx.de> ---
(In reply to Tobias Droste from comment #4)
> I found out why the last CS update caused this issue.
> They siwtched all graphic options to "auto" with the last update and for my
> graphics card it figured out that the highest preference in every setting
> should be the best ones. And with these settings CS:GO is crashing.
>
> I switched backed everything to "low" and I can at least play the game
> again. But the driver should crash with everything set to high.
"should *not* crash" of course :-)
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1532 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 prev parent reply other threads:[~2015-12-13 20:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-12 1:23 [Bug 93360] [radeonsi/llvm] Segfault in CS:GO bugzilla-daemon
2015-12-12 1:25 ` bugzilla-daemon
2015-12-12 3:16 ` bugzilla-daemon
2015-12-12 3:23 ` bugzilla-daemon
2015-12-13 16:31 ` bugzilla-daemon
2015-12-13 20:31 ` bugzilla-daemon
2015-12-13 20:32 ` bugzilla-daemon [this message]
2015-12-13 22:29 ` bugzilla-daemon
2016-01-25 22:27 ` bugzilla-daemon
2016-01-26 3:50 ` bugzilla-daemon
2016-01-26 9:31 ` 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-93360-502-tCOBz78i1M@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).