dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 97524] Invalid sampler settings cause full GPU reset
Date: Mon, 29 Aug 2016 04:06:14 +0000	[thread overview]
Message-ID: <bug-97524-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 97524
           Summary: Invalid sampler settings cause full GPU reset
           Product: Mesa
           Version: git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: minor
          Priority: medium
         Component: Drivers/Gallium/radeonsi
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: dark_sylinc@yahoo.com.ar
        QA Contact: dri-devel@lists.freedesktop.org

Created attachment 126091
  --> https://bugs.freedesktop.org/attachment.cgi?id=126091&action=edit
Bug repro

Running invalid the following GL settings hangs Mesa pretty badly. Sometimes it
says stuck on ring(0)/(3), other times it just hangs; GPU tries to reset but
does a really poor job (at least I can blindly go to tty1 via Ctrl+Alt+F1 then
reboot via Ctrl+Alt+Supr).

Attachment provided to repro the bug.

What is causing it:
Vertex Shader must use samplerBuffer on binding point 0.
Pixel Shader must use samplerCube on binding point 0.
Bind a TBO to binding point 0.

What happens:
Near full system hang, it becomes really unstable. System can be soft-rebooted
but that's it.

What should happen:
All other GPU drivers I tested with handle this gracefully by raising a
GL_INVALID_OPERATION error and continuing rendering the rest normally.

Version tested: Latest git 22cec6dc5e5a3060bc87f4a92871b4f6eef04632

I'm assigning a low priority since this GL setting combination is invalid to
begin with and I want to believe software isn't shipped like this (though
considering other GPU drivers allow to ignore the problem, I wouldn't be fully
surprised if there is faulty software out there...); though I believe the
system shouldn't hang because of this.

GL_VERSION = 4.3.0.0
GL_VENDOR = X.Org
GL_RENDERER = Gallium 0.4 on AMD CAPE VERDE (DRM 2.45.0 / 4.7.0-040700-generic,
LLVM 3.9.0)

uname -r
4.7.0-040700-generic

Cheers

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

[-- Attachment #1.2: Type: text/html, Size: 3578 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:[~2016-08-29  4:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-29  4:06 bugzilla-daemon [this message]
2016-09-02 10:03 ` [Bug 97524] Invalid sampler settings cause full GPU reset bugzilla-daemon
2016-09-03 21:54 ` bugzilla-daemon
2016-09-03 21:54 ` bugzilla-daemon
2016-09-03 21:55 ` bugzilla-daemon
2016-09-12 15:11 ` bugzilla-daemon
2016-09-12 22:00 ` bugzilla-daemon
2016-09-14  0:08 ` bugzilla-daemon
2016-09-14  8:56 ` bugzilla-daemon
2016-09-14 22:01 ` bugzilla-daemon
2016-10-06 13:56 ` 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-97524-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;
as well as URLs for NNTP newsgroup(s).