https://bugs.freedesktop.org/show_bug.cgi?id=100953
Bug ID: 100953
Summary: [ARUBA] Light shaders is very bright in GRID Autosport
on Radeon 8470D
Product: Mesa
Version: 17.1
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: russianneuromancer(a)ya.ru
QA Contact: dri-devel(a)lists.freedesktop.org
Created attachment 131234
--> https://bugs.freedesktop.org/attachment.cgi?id=131234&action=edit
GRID Autosport on Radeon 8470D
Hello!
Please look into attached screenshot.
This issue is not reproducible on Radeon HD 6650M.
Software:
Kubuntu 17.0 x86_64
Linux 4.10
Mesa: 17.1.0rc2
libdrm: 2.4.80
xserver-xorg-video-radeon: 7.9.0
xserver-xorg-core: 1.19.3
Hardware:
AMD A6-6400K with Radeon HD 8470D (ARUBA)
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=100865
Bug ID: 100865
Summary: Unigine Heaven 4 lockups GPU in wireframe mode
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: marvin24(a)gmx.de
QA Contact: dri-devel(a)lists.freedesktop.org
Created attachment 131115
--> https://bugs.freedesktop.org/attachment.cgi?id=131115&action=edit
dmesg output
launched UH4 on RS880 / Kernel 4.10.10 with mesa git
demo runs well until you press "F2" in order to activate wireframe mode, which
causes GPU lockups
tested mesa: 12, 13, 17, 17.1 and git - all same.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=100387
Bug ID: 100387
Summary: War Thunder game has visual errors, missing textures
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: acelists(a)atlas.sk
QA Contact: dri-devel(a)lists.freedesktop.org
Using the War Thunder game on Slackware, Mesa git custom compiled, LLVM 4.0 and
on a RV710 card (512MB video RAM) always produces visual errors. The errors are
not the same at all runs but vary between these problems, e.g. sky being black,
clouds being any color, water is some color without reflections, trees being
blue.
Plane/ground target models are mostly correct, but sometimes they are also
white.
The errors can be seen right in the hangar, but also when playing the game (in
a mission).
I have set the "Old videocard support" in the graphics options in the game.
This has improved things to the state I describe. The game client shows "ultra
low quality" in the right hand corner. I am using the low-res client (HD
textures not downloaded) and the client often prompts to download hi-res
textures which I decline.
Other than this, the game runs correctly, albeit slow on this GPU (5-15FPS).
In the console where I start the game (updater binary) there is a ton of output
like:
EE r600_shader.c:183 r600_pipe_shader_create - translation from TGSI failed !
EE r600_state_common.c:803 r600_shader_select - Failed to build shader variant
(type=1) -1
The line numbers 183 and 803 are always the same.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=99843
Bug ID: 99843
Summary: Geometry Shader - Incorrect Output
Product: Mesa
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: dan(a)jerber.co.uk
QA Contact: dri-devel(a)lists.freedesktop.org
Created attachment 129684
--> https://bugs.freedesktop.org/attachment.cgi?id=129684&action=edit
Typical output
Hi,
I am developing a cross-platform application. I have recently found an issue
that is only present when it is tested on a Ubuntu machine. I have managed to
find a minimal example that shows the issue as follows:
The vertex shader:
#version 150
in vec2 pos;
void main(void)
{
gl_Position = vec4(pos, 0.0, 1.0);
}
The fragment shader:
#version 150
out vec4 outColour;
void main(void)
{
outColour = vec4(1.0f, 1.0f, 1.0f, 1.0f);
}
The geometry shader:
#version 150
layout(points) in;
layout(line_strip, max_vertices = 13) out;
uniform mat4 vpMatrix;
void main()
{
for(int i = 0; i < 13; i++)
{
float polygonAngle = (i * 30) + 90.0f;
vec4 vertexPosition = vec4((sin(radians(polygonAngle)) * 0.5f) +
gl_in[0].gl_Position.x, (cos(radians(polygonAngle)) * 0.5f) +
gl_in[0].gl_Position.y, 0.0f, 1.0f);
gl_Position = vpMatrix * vertexPosition;
EmitVertex();
}
EndPrimitive();
}
The problem occurs when the shader program is used with multiple VBO's. For
example:
3 separate VBO's are created with {-1.0f, 1.0f}, {1.0f, 1.0f}, {1.0f, -1.0f} as
the data. Then, for each repaint:
for(int i = 0; i < 3; i++)
{
Bind array buffer i.
glDrawArrays(GL_POINTS, 0, 1);
}
This produces strange results for the third polygon (shown in the attached
image Output.JPG).
If tested on a Windows 10 machine (exactly the same hardware) or an OSX
machine, the results are as expected (3 regular polygons with 12 sides).
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=96881
Bug ID: 96881
Summary: ViennaCL fails dense_blas-bench-opencl benchmark with
doubles on AMD CYPRESS (DRM 2.43.0, LLVM 3.8.0)
Product: Mesa
Version: 11.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: ubizjak(a)gmail.com
QA Contact: dri-devel(a)lists.freedesktop.org
The dense_blas-bench-opencl benchmark from ViennaCL suite fails with doubles on
AMD CYPRESS (DRM 2.43.0, LLVM 3.8.0):
$ ./dense_blas-bench-opencl
----------------------------------------------
Device Info
----------------------------------------------
Name: AMD CYPRESS (DRM 2.43.0, LLVM 3.8.0)
Vendor: AMD
Type: GPU
Available: 1
Max Compute Units: 10
Max Work Group Size: 256
Global Mem Size: 1073741824
Local Mem Size: 32768
Local Mem Type: 1
Host Unified Memory: 1
Benchmark : BLAS
----------------
sCOPY : 64.3 GB/s
sAXPY : 95.4 GB/s
sDOT : 85.3 GB/s
sGEMV-N : 20.8 GB/s
sGEMV-T : 44.3 GB/s
sGEMM-NN : 126 GFLOPs/s
sGEMM-NT : 87.6 GFLOPs/s
sGEMM-TN : 90.5 GFLOPs/s
sGEMM-TT : 72.3 GFLOPs/s
----
Build Status = -2 ( Err = -11 )
Log: unsupported call to function __subdf3 in av_cpu
Sources: #pragma OPENCL EXTENSION cl_khr_fp64 : enable
__kernel void av_cpu(
__global double * vec1,
uint4 size1,
...
It looks like DFmode (double) instructions are not enabled correctly in LLVM
for targets that report cl_khr_fp64 extension.
clinfo reports:
Number of platforms 1
Platform Name Clover
Platform Vendor Mesa
Platform Version OpenCL 1.1 MESA 11.2.2
Platform Profile FULL_PROFILE
Platform Extensions cl_khr_icd
Platform Extensions function suffix MESA
Platform Name Clover
Number of devices 1
Device Name AMD CYPRESS (DRM 2.43.0, LLVM
3.8.0)
Device Vendor AMD
Device Vendor ID 0x1002
Device Version OpenCL 1.1 MESA 11.2.2
Driver Version 11.2.2
Device OpenCL C Version OpenCL C 1.1
Device Type GPU
Device Profile FULL_PROFILE
Max compute units 10
Max clock frequency 850MHz
Max work item dimensions 3
Max work item sizes 256x256x256
Max work group size 256
Preferred work group size multiple 64
Preferred / native vector sizes
char 16 / 16
short 8 / 8
int 4 / 4
long 2 / 2
half 0 / 0 (n/a)
float 4 / 4
double 2 / 2
(cl_khr_fp64)
Half-precision Floating-point support (n/a)
Single-precision Floating-point support (core)
Denormals No
Infinity and NANs Yes
Round to nearest Yes
Round to zero No
Round to infinity No
IEEE754-2008 fused multiply-add No
Support is emulated in software No
Correctly-rounded divide and sqrt operations No
Double-precision Floating-point support (cl_khr_fp64)
Denormals Yes
Infinity and NANs Yes
Round to nearest Yes
Round to zero Yes
Round to infinity Yes
IEEE754-2008 fused multiply-add Yes
Support is emulated in software No
Correctly-rounded divide and sqrt operations No
...
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=99510
Bug ID: 99510
Summary: cl_khr_fp64 is reported as supported, but is not, on
CAYMAN
Product: Mesa
Version: 13.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: benjiwiebe14(a)gmail.com
QA Contact: dri-devel(a)lists.freedesktop.org
On CAYMAN, cl_khr_fp64 is listed as a supported extension in clinfo, and
therefore also makes some kernels fail to compile due to their trying to
compile in things that need cl_khr_fp64 support. This causes clpeak to fail
with 'unsupported call to function __floatunsidf in compute_dp_v1'.
If you need more information I will be happy to provide more.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=99029
Bug ID: 99029
Summary: VCE VAAPI segfault using ffmpeg
Product: Mesa
Version: 13.0
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: serafean(a)gmail.com
QA Contact: dri-devel(a)lists.freedesktop.org
lspci:00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Trinity [Radeon HD 7480D]
libva info: Trying to open /usr/lib64/va/drivers/r600_drv_video.so
libva info: Found init function __vaDriverInit_0_39
libva info: va_openDriver() returns 0
vainfo: VA-API version: 0.39 (libva 1.7.3)
vainfo: Driver version: mesa gallium vaapi
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple : VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main : VAEntrypointVLD
VAProfileVC1Advanced : VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileNone : VAEntrypointVideoProc
commandline:
ffmpeg -vaapi_device /dev/dri/renderD128 -i Elephants_Dream_HD.avi -vf
format=rgba,hwupload -bf 0 -c:v h264_vaapi test.mkv
run on a console over ssh.
backtrace:
#0 0x00007f4004a58e3f in create (enc=0x19ed530) at
/var/tmp/portage/media-libs/mesa-13.0.2/work/mesa-13.0.2/src/gallium/drivers/radeon/radeon_vce_40_2_2.c:98
#1 0x00007f4004a5cd3f in rvce_begin_frame (encoder=0x19ed530,
source=0x16e1a70, picture=0x19131d8) at
/var/tmp/portage/media-libs/mesa-13.0.2/work/mesa-13.0.2/src/gallium/drivers/radeon/radeon_vce.c:288
#2 0x00007f400490cdec in vlVaEndPicture (ctx=<optimized out>, context_id=23)
at
/var/tmp/portage/media-libs/mesa-13.0.2/work/mesa-13.0.2/src/gallium/state_trackers/va/picture.c:572
#3 0x00007f401cfcf08f in vaEndPicture (dpy=0x1691c20, context=23) at
/var/tmp/portage/x11-libs/libva-1.7.3/work/libva-1.7.3/va/va.c:1232
#4 0x00007f401e202a9b in vaapi_encode_issue (avctx=avctx@entry=0x16e5060,
pic=pic@entry=0x1745500) at src/libavcodec/vaapi_encode.c:387
#5 0x00007f401e202c16 in vaapi_encode_step (avctx=avctx@entry=0x16e5060,
target=target@entry=0x1745500) at src/libavcodec/vaapi_encode.c:587
#6 0x00007f401e202fe7 in ff_vaapi_encode2 (avctx=0x16e5060, pkt=0x190fa60,
input_image=<optimized out>, got_packet=0x7ffc264290d4) at
src/libavcodec/vaapi_encode.c:867
#7 0x00007f401e1f6d15 in avcodec_encode_video2 (avctx=avctx@entry=0x16e5060,
avpkt=0x190fa60, frame=frame@entry=0x19ad200,
got_packet_ptr=got_packet_ptr@entry=0x7ffc264290d4) at
src/libavcodec/utils.c:1994
#8 0x00007f401e1f6fda in do_encode (avctx=0x16e5060, frame=0x19ad200,
got_packet=0x7ffc264290d4) at src/libavcodec/utils.c:2939
#9 0x00007f401e1fc167 in avcodec_send_frame (avctx=avctx@entry=0x16e5060,
frame=0x19ad200) at src/libavcodec/utils.c:2988
#10 0x0000000000420fdd in do_video_out (of=of@entry=0x1745be0,
ost=ost@entry=0x16e4e00, next_picture=next_picture@entry=0x19ad200,
sync_ipts=<optimized out>, sync_ipts(a)entry=-7.62939453125e-06) at
src/ffmpeg.c:1251
#11 0x000000000042266f in reap_filters (flush=flush@entry=0) at
src/ffmpeg.c:1451
#12 0x0000000000409316 in transcode_step () at src/ffmpeg.c:4343
#13 transcode () at src/ffmpeg.c:4387
#14 main (argc=<optimized out>, argv=<optimized out>) at src/ffmpeg.c:4592
Testing patches is no problem.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=98738
Bug ID: 98738
Summary: AMD E450| HD 6320 - crashing playback with kodi, maybe
vdpau problem, mesa, r600
Product: Mesa
Version: unspecified
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: blffkyzp(a)sharklasers.com
QA Contact: dri-devel(a)lists.freedesktop.org
Created attachment 127981
--> https://bugs.freedesktop.org/attachment.cgi?id=127981&action=edit
dmesg
Since many kernel versions there is this one bug that happens irregular.
When wathcing live-tv on kodi with tv-headend and the TV-Channel changes the
frequency by itself and the live-tv follows (nothing that special in many
countries) then whole system crashes and kodi restarts.
I attached all logfiles i have saved. The last 2-3 ones (date in logfile) are
100% shure from this bug. The other ones "could" be from some other error, but
are most likely also from this bug.
xorg and dmesg logfiles are from lastest crash log.
Hardware is AMD E450 with build in HD6320 GPU.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=98494
Bug ID: 98494
Summary: Screen flickering in Black Mesa game
Product: Mesa
Version: 13.0
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: wolfgang-wallner(a)gmx.at
QA Contact: dri-devel(a)lists.freedesktop.org
The Black Mesa game has been released for Linux.[1]
Unfortunately, the game flickers every 2-3 seconds when I run it on my discrete
AMD card.
System:
HP Pavilion Laptop
Intel Sandybridge
AMD HD6770M discrete graphics card
8GB RAM
Kubuntu 16.10 with Kernel 4.8 (default)
Mesa 13.1.0-devel (according to kinfocenter) from the oibaf PPA
KDE Plasma 5.7.5
The screen flickering does not happen if I run the game on the integrated Intel
graphics card.
I tried the following without effect:
*) Changing graphics settings
*) Enabling/disabling desktop effects
*) Changing from two monitors to only one monitor
The bug is also reported to the Black Mesa developers in the steam forums [2].
If I can provide any additional information, please let me know.
[1]
http://steamcommunity.com/games/362890/announcements/detail/548704237438813…
[2]
http://steamcommunity.com/app/362890/discussions/0/312265327168384714/?ctp=…
--
You are receiving this mail because:
You are the assignee for the bug.