All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 101672] radeonsi: 3D engines causing frequent GPU lockups
Date: Sun, 02 Jul 2017 15:24:40 +0000	[thread overview]
Message-ID: <bug-101672-502-e0pYSFys51@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-101672-502@http.bugs.freedesktop.org/>


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

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

--- Comment #7 from MirceaKitsune <sonichedgehog_hyperblast00@yahoo.com> ---
Created attachment 132397
  --> https://bugs.freedesktop.org/attachment.cgi?id=132397&action=edit
mesa_err.log

I was able to find an important clue, while running Xonotic using the following
environment variables:

MESA_DEBUG=1
MESA_LOG_FILE=/foo/bar/mesa_err.log

A log is generated and readable after restarting the machine. It only contains
one line, but that looks like it might address the cause:

Mesa: User error: GL_INVALID_OPERATION in glGetQueryObjectiv(out of bounds)

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

[-- Attachment #1.2: Type: text/html, Size: 1622 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-07-02 15:24 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-02  0:22 [Bug 101672] radeonsi: 3D engines causing frequent GPU lockups bugzilla-daemon
2017-07-02  0:23 ` bugzilla-daemon
2017-07-02  0:24 ` bugzilla-daemon
2017-07-02  0:24 ` bugzilla-daemon
2017-07-02  0:25 ` bugzilla-daemon
2017-07-02  0:25 ` bugzilla-daemon
2017-07-02  0:26 ` bugzilla-daemon
2017-07-02 15:24 ` bugzilla-daemon [this message]
2017-07-11 22:13 ` bugzilla-daemon
2017-07-24 11:59 ` bugzilla-daemon
2017-07-26 22:10 ` bugzilla-daemon
2017-07-26 22:11 ` bugzilla-daemon
2017-07-26 22:12 ` bugzilla-daemon
2017-07-26 22:12 ` bugzilla-daemon
2017-07-26 22:13 ` bugzilla-daemon
2017-07-26 22:13 ` bugzilla-daemon
2017-07-26 22:14 ` bugzilla-daemon
2017-07-26 22:39 ` bugzilla-daemon
2017-07-27 14:52 ` bugzilla-daemon
2017-07-29 13:31 ` bugzilla-daemon
2017-08-01 12:17 ` bugzilla-daemon
2017-08-04 12:33 ` bugzilla-daemon
2018-02-22  0:06 ` bugzilla-daemon
2018-02-22  0:07 ` bugzilla-daemon
2018-02-22  7:34 ` bugzilla-daemon
2018-02-26 21:28 ` bugzilla-daemon
2018-02-27 12:02 ` bugzilla-daemon
2018-03-09 21:39 ` bugzilla-daemon
2018-03-09 21:45 ` 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-101672-502-e0pYSFys51@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.