dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 90217] Counter Strike Global Offensive: GPU fault after a while
Date: Wed, 29 Apr 2015 21:58:34 +0000	[thread overview]
Message-ID: <bug-90217-502-AIAej1481P@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-90217-502@http.bugs.freedesktop.org/>


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

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

--- Comment #2 from Christoph Haag <haagch@frickel.club> ---
Created attachment 115456
  --> https://bugs.freedesktop.org/attachment.cgi?id=115456&action=edit
dmesg with graphical output hang

It can also have more severe consequences and require a reboot, see dmesg.

I'll use R600_DEBUG=ps,vs,gs next time. It can take quite a while to trigger
it, I hope it won't produce too much data.

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

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

  parent reply	other threads:[~2015-04-29 21:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-28 16:34 [Bug 90217] Counter Strike Global Offensive: GPU fault after a while bugzilla-daemon
2015-04-29 14:56 ` bugzilla-daemon
2015-04-29 21:58 ` bugzilla-daemon [this message]
2015-04-29 23:43 ` bugzilla-daemon
2015-05-22 21:35 ` bugzilla-daemon
2015-08-01  9:27 ` bugzilla-daemon
2015-08-04  1:58 ` bugzilla-daemon
2015-08-04  1:58 ` bugzilla-daemon
2018-04-03  3:36 ` bugzilla-daemon
2018-04-03 13:54 ` bugzilla-daemon
2019-09-25 17:52 ` 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-90217-502-AIAej1481P@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