https://bugs.freedesktop.org/show_bug.cgi?id=108641
Bug ID: 108641
Summary: Interlaced dark lines in XCOM2 (UE3.5) on Aruba and
Turks
Product: Mesa
Version: 18.2
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: steelwinged(a)gmail.com
QA Contact: dri-devel(a)lists.freedesktop.org
Created attachment 142355
--> https://bugs.freedesktop.org/attachment.cgi?id=142355&action=edit
in-game screenshot
Game engine rendering outputs are interlaced with dark lines on r600.
Tested on: 7660G (Aruba) and 7670M (Turks) with Mesa 18.2.4.
Renderdoc captures have been uploaded here:
https://www32.zippyshare.com/v/G74cEAp5/file.html
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=108507
Bug ID: 108507
Summary: [rv790] Broken ground textures in World of Tanks
Product: Mesa
Version: 18.2
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: grantipak(a)gmail.com
QA Contact: dri-devel(a)lists.freedesktop.org
Created attachment 142119
--> https://bugs.freedesktop.org/attachment.cgi?id=142119&action=edit
Broken ground textures
Radeon HD 4890, ArchLinux x64, mesa 18.2.2, llvm 7.0.0
Screenshot in attachment
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=108321
Bug ID: 108321
Summary: rv610: corrupt shader output with SB if_conversion
optimization pass
Product: Mesa
Version: git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: nicholasbishop(a)gmail.com
QA Contact: dri-devel(a)lists.freedesktop.org
Created attachment 141984
--> https://bugs.freedesktop.org/attachment.cgi?id=141984&action=edit
rv610 sbdump
I'm debugging some graphics corruption in Chromium on an iMac7,1 with rv610
graphics. Basically an area of the application has randomish blocks of color,
like it's reading from an uninitialized texture.
I've narrowed the problem down to a fragment shader:
varying mediump vec2 _uv_texCoord;
uniform lowp sampler2D _ulut_texture;
uniform mediump float _ulut_size;
mediump vec4 _uLUT(in lowp sampler2D _usampler, in mediump vec3 _upos, in
mediump float _usize){
(_upos *= (_usize - 1.0));
mediump float _ulayer = min(floor(_upos.z), (_usize - 2.0));
(_upos.xy = ((_upos.xy + vec2(0.51234001, 0.51234001)) / _usize));
(_upos.y = ((_upos.y + _ulayer) / _usize));
return mix(texture2D(_usampler, _upos.xy), texture2D(_usampler, (_upos.xy
+ vec2(0, (1.0 / _usize)))), (_upos.z - _ulayer));
}
void main(){
mediump vec2 _utexCoord = _uv_texCoord;
mediump vec4 _utexColor = texture2D(_us_texture, _utexCoord);
if ((_utexColor.w > 0.0))
{
(_utexColor.xyz /= _utexColor.w);
}
(_utexColor.xyz = _uLUT(_ulut_texture, _utexColor.xyz, _ulut_size).xyz);
(_utexColor.xyz *= _utexColor.w);
(gl_FragColor = vec4(_utexColor.xyz, 1.0));
}
(Note that in the original shader "0.51234001" is just "0.5", I just changed it
to make grepping easier.) I played around with changes to the _uLUT function,
and I found that any mixing of the two samples seems to trigger the bug, e.g. I
can mix with a constant 0.5 and the bug still happens. I also tried replacing
"mix" with an explicit a*(x-1)+b*x; no change.
I found that disabling SB fixed the issue, and in particular just commenting
out the "if_conversion" SB pass fixes the issue.
I've attached the full sbdump output. Please let me know if there are more
details I can provide that would help.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=108030
Bug ID: 108030
Summary: Does not work discrete graphics CERAR (6370M)
Product: Mesa
Version: 18.1
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: ilya(a)ilya.pp.ua
QA Contact: dri-devel(a)lists.freedesktop.org
Only integrated graphics Intel works.
When running graphics applications with DRI_PRIME=1, this application or
segfault or show a black screen (sometimes playing a sound).
Sometimes, with some probability, this leads to crash Xorg.
In the logs there is nothing suspicious or any errors, only segfault.
I attached some logs, if this is not enough, then tell me which file or output
of which command I have to attach.
I want to either with DRI_PRIME=1 worked discrete graphics or worked all the
time only discrete graphics.
Is this possible on the open drivers with the latest software?
Notebook: HP Pavilion dv6 with hybrid graphics (Intel 3000HD/Radeon HD 6370M
CEDAR)
OS: openSUSE Tumbleweed (4.18.8-1-default, LLVM 6.0.1, Mesa 18.1.7)
sudo cat /sys/kernel/debug/vgaswitcheroo/switch
0:DIS: :DynOff:0000:01:00.0
1:IGD:+:Pwr:0000:00:02.0
2:DIS-Audio: :DynOff:0000:01:00.1
glxinfo | grep OpenGL
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) Ironlake Mobile
OpenGL version string: 2.1 Mesa 18.1.7
OpenGL shading language version string: 1.20
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 2.0 Mesa 18.1.7
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 1.0.16
OpenGL ES profile extensions:
DRI_PRIME=1 glxinfo | grep OpenGL
OpenGL vendor string: X.Org
OpenGL renderer string: AMD CEDAR (DRM 2.50.0 / 4.18.8-1-default, LLVM 6.0.1)
OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.1.7
OpenGL core profile shading language version string: 3.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.1 Mesa 18.1.7
OpenGL shading language version string: 1.40
OpenGL context flags: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.1 Mesa 18.1.7
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10
OpenGL ES profile extensions:
dmesg | grep -i radeon
[ 8604.934090] radeon 0000:01:00.0: WB enabled
[ 8604.934094] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr
0x0000000020000c00 and cpu addr 0x00000000615bbe52
[ 8604.934095] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr
0x0000000020000c0c and cpu addr 0x000000001a943f21
[ 8604.934469] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr
0x000000000005c418 and cpu addr 0x000000006515891a
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=107666
Bug ID: 107666
Summary: st_sampler_view.c:546 assert
Product: Mesa
Version: 18.2
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: martin(a)serafean.cz
QA Contact: dri-devel(a)lists.freedesktop.org
mesa 18.2.0_rc4
lspci:
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Cayman PRO [Radeon HD 6950]
glxinfo:
Device: AMD CAYMAN (DRM 2.50.0 / 4.17.14-gentoo, LLVM 6.0.1) (0x6719)
Version: 18.2.0
Using Kodi to watch tv using the HTSP plugin, using VDPAU for decoding:
kodi.bin: ../mesa-18.2.0-rc4/src/mesa/state_tracker/st_sampler_view.c:546:
st_get_texture_sampler_view_from_stobj: Assertion `stObj->level_override ||
last_level(stObj) == view->u.tex.last_level' failed.
VAAPI decoding works.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=107454
Bug ID: 107454
Summary: BLENDER 2.8 principled BSDF shader and shadow are
broken in EEVEE on mesa gallium r600g gpu
Product: Mesa
Version: git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: Drivers/Gallium/r600
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: amonpaike(a)gmail.com
QA Contact: dri-devel(a)lists.freedesktop.org
on the new blender 2.8 under development some shaders and projections of
shadows are broken .. I do not know how to describe the problem technically, I
have already reported the problem to the bug list of blender developers,
although I know that the problem is probably the mesa drivers, because on my
laptop that has two gpu, with the intel gpu the graphics is perfect, with the
gpu amd I have these problems of shading.
For a specific description of the problem, refer to this bug report
https://developer.blender.org/T56211
(the tests were done on the latest mesa drivers built daily by padoka ppa, with
the stable drivers of ubuntu 18.04 eevee shading was totally unusable, so the
situation has improved significantly)
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=107448
Bug ID: 107448
Summary: [r600g] 2 of 5 piglit sanity tests fail (PCIe, ppc64,
mesa-18.1.5)
Product: Mesa
Version: unspecified
Hardware: PowerPC
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: erhard_f(a)mailbox.org
QA Contact: dri-devel(a)lists.freedesktop.org
Created attachment 140928
--> https://bugs.freedesktop.org/attachment.cgi?id=140928&action=edit
results from 'pigllit run sanity' (18.1.5)
Machine is a PowerMac G5 11,2 + Radeon HD 6450.
Command
/root/build/piglit/bin/shader_runner
/root/build/piglit/test/spec/arb_tessellation_shader/execution/sanity.shader_test
-auto -fbo
Stdout
Probe color at (0,0)
Expected: 0 255 0 255
Observed: 25 25 25 25
Test failure on line 57
Stderr
Mesa: User error: GL_INVALID_ENUM in
lGetFramebufferAttachmentParameteriv(invalid attachment GL_NONE)
Command
/root/build/piglit/bin/glsl-1.50-transform-feedback-builtins -auto -fbo
Stdout
Incorrect data for 'gl_Layer' output 0. Expected 1, got 16777216.
Incorrect data for 'gl_Layer' output 1. Expected 3, got 50331648.
Incorrect data for 'gl_Layer' output 2. Expected 5, got 83886080.
Incorrect data for 'gl_ViewportIndex' output 0. Expected 1, got 16777216.
Incorrect data for 'gl_ViewportIndex' output 1. Expected 2, got 33554432.
Incorrect data for 'gl_ViewportIndex' output 2. Expected 3, got 50331648.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=107169
GitLab Migration User <gitlab-migration(a)fdo.invalid> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |MOVED
Status|NEEDINFO |RESOLVED
--- Comment #7 from GitLab Migration User <gitlab-migration(a)fdo.invalid> ---
-- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has been
closed from further activity.
You can subscribe and participate further through the new bug through this link
to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/641.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=107150
Bug ID: 107150
Summary: GPU restarts when some games are launched
Product: Mesa
Version: 18.0
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: shpalikvitalik(a)gmail.com
QA Contact: dri-devel(a)lists.freedesktop.org
When launching some games such as Dirt Showdown, Dirt 2 (wine), War Thunder
(native), a cyclic restart of graphics occurs. During the launch of the Dirt
Showdown game, a black screen appears, then the display turns off and the phone
turns on, the game sounds. Then it repeats many times and then the system
hangs. It helps only the power off. It is also observed with other listed
games.
I ran games with the variable R600_DEBUG = nosb it helped only with War Thunder
(native), with others not.I remember that with mesa 17.x.3, Dirt Showdown was
launched exactly. The problem would not be so important if I had to register at
startup R600_DEBUG = nosb, but it is not. I would like that this error was
detected and did not interfere launch of similar applications.In advance thanks
to those who will respond to help in solving the problem.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=106892
Bug ID: 106892
Summary: GPU hang with radeon glx driver
Product: Mesa
Version: 18.0
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: Drivers/Gallium/r600
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: sur3(a)gmx.de
QA Contact: dri-devel(a)lists.freedesktop.org
Created attachment 140126
--> https://bugs.freedesktop.org/attachment.cgi?id=140126&action=edit
dmesg from xonotic hang
Hi I'm using Mesa 18.1.1, when trying to play OpenGL games (e.g. Xonotic,
Minetest) with my Radeon HD 4670 I get some graphics glitches and then the GPU
is hanging and the X Server resets and until a complete restart mesa seems to
use some VMware LLVMpipe driver then.
Also the driver seems to spam my dmesg with annoying EDID messages.
--
You are receiving this mail because:
You are the assignee for the bug.