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 107857] [apitrace] GPU hang on VEGA10
Date: Fri, 07 Sep 2018 10:51:42 +0000	[thread overview]
Message-ID: <bug-107857-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 107857
           Summary: [apitrace] GPU hang on VEGA10
           Product: Mesa
           Version: git
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/radeonsi
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: joseph.kucia@gmail.com
        QA Contact: dri-devel@lists.freedesktop.org

Created attachment 141472
  --> https://bugs.freedesktop.org/attachment.cgi?id=141472&action=edit
apitrace

This can be reproduced reliably using the attached apitrace.

OpenGL renderer string: Radeon RX Vega (VEGA10, DRM 3.23.0, 4.15.5-gentoo, LLVM
6.0.0)
OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.3.0-devel
(git-1c7a2433b2)

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

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

             reply	other threads:[~2018-09-07 10:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-07 10:51 bugzilla-daemon [this message]
2018-09-23 22:53 ` [Bug 107857] GPU hang - GS_EMIT without shader outputs bugzilla-daemon
2018-09-23 22:57 ` bugzilla-daemon
2018-10-02 21: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-107857-502@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