From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 105218] Regresion in 847d0a393d7f0f967f39302900d5330f32b804c8
Date: Thu, 22 Feb 2018 23:40:47 +0000 [thread overview]
Message-ID: <bug-105218-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2501 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=105218
Bug ID: 105218
Summary: Regresion in 847d0a393d7f0f967f39302900d5330f32b804c8
Product: Mesa
Version: git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: blocker
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
Our Terrain sample from Ogre 2.1 uses a compute shader to generate the shadows
of the terrain, and later uses a special vs & ps to render the terrain.
What's special about that sample over the rest (that run fine) are:
1. The compute shader that generates the shadows
(https://bitbucket.org/sinbad/ogre/src/09181053ca69f4760b655c2eed5b5ca7d62fd7bc/Samples/Media/2.0/scripts/materials/Tutorial_Terrain/GLSL/TerraShadowGenerator.glsl?at=v2-1&fileviewer=file-view-default).
The heigthmap is in format R16_UNORM, the generated shadows texture is in
RGB10A2
2. A PS that generates the normals
(https://bitbucket.org/sinbad/ogre/src/09181053ca69f4760b655c2eed5b5ca7d62fd7bc/Samples/Media/2.0/scripts/materials/Tutorial_Terrain/GLSL/GpuNormalMapper_ps.glsl?at=v2-1&fileviewer=file-view-default).
The normals' texture are in RGB10A2
3. The VS has no vertex buffer bound, but rather relies on gl_VertexID and
integer ops
(https://bitbucket.org/sinbad/ogre/src/09181053ca69f4760b655c2eed5b5ca7d62fd7bc/Samples/Media/Hlms/Terra/GLSL/VertexShader_vs.glsl?at=v2-1&fileviewer=file-view-default#VertexShader_vs.glsl-66)
and reads the heightmap.
After commit 847d0a393d7f0f967f39302900d5330f32b804c8 and at least until latest
from today, running this sample causes an entire system freeze: Mouse cursor is
the only thing that responds. Keyboard does not respond, hard resetting is the
only way and tends to corrupt files in the drive (This was painful to bisect).
Before this commit the sample behaves as expected.
My GPU is a Radeon RX 560 2GB
I can provide a binary with the failing sample, or instructions on how to build
from source (https://ogrecave.github.io/ogre/api/2.1/SettingUpOgreLinux.html).
Whatever you need.
I'm flagging this as blocker because of the security implications of freezing
the entire system with ease.
Cheers
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 4616 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 reply other threads:[~2018-02-22 23:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-22 23:40 bugzilla-daemon [this message]
2018-03-30 12:08 ` [Bug 105218] Regresion in 847d0a393d7f0f967f39302900d5330f32b804c8 bugzilla-daemon
2018-03-30 12:44 ` bugzilla-daemon
2018-03-30 16:36 ` bugzilla-daemon
2018-03-30 16:40 ` bugzilla-daemon
2018-03-30 23:51 ` bugzilla-daemon
2018-03-31 0:39 ` bugzilla-daemon
2018-04-01 19:41 ` bugzilla-daemon
2018-04-01 19:42 ` 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-105218-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 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.