From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 97524] Invalid sampler settings cause full GPU reset
Date: Mon, 12 Sep 2016 15:11:59 +0000 [thread overview]
Message-ID: <bug-97524-502-EraqgtBZDH@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-97524-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 791 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=97524
--- Comment #5 from Nicolai Hähnle <nhaehnle@gmail.com> ---
I've now tried your sample with Verde, and cannot reproduce it there either.
The logs you have submitted are unfortunately not very useful, because all I
see are messages about ring stalls and reset attempts. Are there any messages
_before_ that?
To be honest, I don't see what the problem could be. Running it with a debug
build (which shows all OpenGL errors) shows quite clearly that the bad state is
caught at program link time, which then leads to the bad program not being
used.
One thing that catches my eye is that your glxinfo says DRM 2.45.0, while mine
says DRM 2.47.0.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1566 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
next prev parent reply other threads:[~2016-09-12 15:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-29 4:06 [Bug 97524] Invalid sampler settings cause full GPU reset bugzilla-daemon
2016-09-02 10:03 ` 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 [this message]
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-EraqgtBZDH@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).