All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 90284] GPU lockup with DOTA2
Date: Wed, 06 May 2015 14:45:16 +0000	[thread overview]
Message-ID: <bug-90284-502-pZuZj50R0J@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-90284-502@http.bugs.freedesktop.org/>


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

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

--- Comment #5 from Trippler <niklas@trippler.no> ---
(In reply to Trippler from comment #4)
> Created attachment 115595 [details]
> journalctl -r -x --boot=-1 when recreating the crash with R600_DEBUG=ps,vs,gs

Done. I added two logs - "output_steam.gz" which is the output of the program,
and "journal_log_with_debug_ps_vs_gs.gz" which is the output of "journalctl
--boot=-1 -r -x"

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

[-- Attachment #1.2: Type: text/html, Size: 1628 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-05-06 14:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-02 17:23 [Bug 90284] radeon crashes (ring 0 stall) with GPU fault detected: 147, and *ERROR* radeon: dpm resume failed bugzilla-daemon
2015-05-02 17:24 ` bugzilla-daemon
2015-05-05 16:15 ` [Bug 90284] GPU lockup with DOTA2 bugzilla-daemon
2015-05-06 14:16 ` bugzilla-daemon
2015-05-06 14:43 ` bugzilla-daemon
2015-05-06 14:44 ` bugzilla-daemon
2015-05-06 14:45 ` bugzilla-daemon [this message]
2015-05-07  3:40 ` bugzilla-daemon
2015-05-08 10:22 ` bugzilla-daemon
2015-05-08 10:23 ` bugzilla-daemon
2015-05-09 10:17 ` bugzilla-daemon
2015-10-17 17:27 ` bugzilla-daemon
2016-05-24 19:16 ` bugzilla-daemon
2016-05-25 14:30 ` bugzilla-daemon
2018-04-03  3: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-90284-502-pZuZj50R0J@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.