From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 92301] Unigine Sanctuary freeze-crashes R390X
Date: Wed, 07 Oct 2015 10:12:04 +0000 [thread overview]
Message-ID: <bug-92301-502-gnQAs1R0NV@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-92301-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1516 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=92301
--- Comment #12 from MC Return <mc.return@gmx.net> ---
(In reply to Michel Dänzer from comment #10)
> (In reply to MC Return from comment #8)
> > GLShader::loadFragment(): error in
> > "core/shaders/render/fragment_occlusion_blur.shader" file
> > defines:
> > UNKNOWN,QUALITY_LOW,QUALITY_MEDIUM,QUALITY_HIGH,MULTISAMPLE_0,USE_INSTANCING,
> > USE_TEXTURE_ARRAY,USE_DEFERRED,USE_TRANSLUCENT,USE_PARALLAX,USE_OCCLUSION,
> > USE_REFLECTION,OPENGL,USE_PSEUDO_INSTANCING,USE_PSEUDO_TRANSFORM,
> > USE_ARB_SAMPLE_SHADING,USE_ARB_TEXTURE_MULTISAMPLE,HAS_ARB_DRAW_INSTANCED
> > 0:511(15): error: no function with name 'texelFetch2DOffset'
>
> These errors may indicate that it's not picking up the correct drirc
> configuration. Does it work if you set the following environment variables
> for running it:
>
> LIBGL_DEBUG=verbose force_glsl_extensions_warn=true
> disable_blend_func_extended=true
>
> If not, please provide the corresponding terminal output and log file again.
I set those env vars, but the result was exactly the same - sanctuary crashed
the machine after a few seconds running, but it showed these errors after
changing screens to console mode:
[drm: ci_dpm_enable [radeon]] *ERROR* ci_start_dpm failed
[drm: radeon_pm_resume [radeon]] *ERROR* radeon: dpm resume failed
[drm: radeon_pm_resume [radeon]] *ERROR* radeon: dpm resume failed
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2470 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-10-07 10:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-05 21:15 [Bug 92301] Unigine Sanctuary freeze-crashes R390X bugzilla-daemon
2015-10-06 1:33 ` bugzilla-daemon
2015-10-06 8:21 ` bugzilla-daemon
2015-10-06 8:25 ` bugzilla-daemon
2015-10-06 8:32 ` bugzilla-daemon
2015-10-06 8:48 ` bugzilla-daemon
2015-10-06 8:55 ` bugzilla-daemon
2015-10-06 9:18 ` bugzilla-daemon
2015-10-06 9:26 ` bugzilla-daemon
2015-10-07 3:39 ` bugzilla-daemon
2015-10-07 3:48 ` bugzilla-daemon
2015-10-07 10:05 ` bugzilla-daemon
2015-10-07 10:12 ` bugzilla-daemon [this message]
2015-10-07 10:26 ` bugzilla-daemon
2015-10-09 8:48 ` bugzilla-daemon
2015-10-09 12:07 ` bugzilla-daemon
2015-10-09 12:23 ` 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-92301-502-gnQAs1R0NV@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