From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 104295] Launching counter strike global offensive fails after update from 17.2 to 17.3
Date: Thu, 28 Dec 2017 20:19:53 +0000 [thread overview]
Message-ID: <bug-104295-502-qFZsfKycHI@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-104295-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 852 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=104295
--- Comment #5 from Emil Velikov <emil.l.velikov@gmail.com> ---
(In reply to sleepyoh from comment #4)
> Running Arch, Had the same problem but is since today solved.
>
> Today there was updates from mesa (17.3.0-2 -> 17.3.1-2) and xorg-server
> (1.19.5-1 -> 1.19.6-2) wich solved this problem, working fine again.
>
> https://bbs.archlinux.org/viewtopic.php?id=232925
>
> I had problems for weeks, now working fine, resolved for me.
I fear your observation is unrelated - Mesa 17.3.1 includes commit
5ac9d91ee3d897016d54e970a977c3fbbbe2488e, which
a) is exclusive for Intel (Skylake or newer)
b) resolved a GPU lockup
While the issue here seems to be:
a) radeonsi hardware
b) program crash
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1860 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 prev parent reply other threads:[~2017-12-28 20:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-16 21:13 [Bug 104295] Launching counter strike global offensive fails after update from 17.2 to 17.3 bugzilla-daemon
2017-12-16 21:16 ` bugzilla-daemon
2017-12-18 11:19 ` bugzilla-daemon
2017-12-18 12:32 ` bugzilla-daemon
2017-12-28 18:52 ` bugzilla-daemon
2017-12-28 20:19 ` bugzilla-daemon [this message]
2017-12-29 1:32 ` bugzilla-daemon
2018-01-02 14:22 ` bugzilla-daemon
2018-01-02 14:22 ` 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-104295-502-qFZsfKycHI@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