https://bugs.freedesktop.org/show_bug.cgi?id=105533
Bug ID: 105533
Summary: [r600g] Trying UVD causes my system crash and hang on
RV730
Product: Mesa
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: blocker
Priority: medium
Component: Drivers/Gallium/r600
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: ken20001(a)ukr.net
QA Contact: dri-devel(a)lists.freedesktop.org
Trying UVD causes my system crash and hang on my RV730. Unfortunately I was not
able to get any backtrace logs after rebooting cause it is not saves.
I tried:
mpv -vo vdpau -hwdec=vdpau
mpt -vo vaapi -hwdec=vaapi
it starts to play for a second but then display becomes black and only hardware
reset can reanimate my system.
Kubuntu 18.04
Linux: 4.15.0-12-generic x86_64
mesa-vdpau-drivers: 18.0.0~rc4-1ubuntu3
libva2: 2.1.0-1
$ lspci | grep -i vga
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV730
XT [Radeon HD 4670]
$ glxinfo | grep -i version
server glx version string: 1.4
client glx version string: 1.4
GLX version: 1.4
Version: 18.0.0
Max core profile version: 3.3
Max compat profile version: 3.0
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.0
OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.0.0-rc4
OpenGL core profile shading language version string: 3.30
OpenGL version string: 3.0 Mesa 18.0.0-rc4
OpenGL shading language version string: 1.30
OpenGL ES profile version string: OpenGL ES 3.0 Mesa 18.0.0-rc4
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=105463
Bug ID: 105463
Summary: [r600] 4210 piglit failures, 55 crashes, 14 warnings
on ppc (PCIe, ppc64, mesa-18.0.0_rc4)
Product: Mesa
Version: git
Hardware: PowerPC
OS: 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 138034
--> https://bugs.freedesktop.org/attachment.cgi?id=138034&action=edit
results from 'pigllit run all'
Just wanted to give some overlook on the state of current mesa on Big Endian
PowerPC. In case someone may be interested or has a surplus of spare time. ;)
The card is a Radeon HD 6450 (no Mac-BIOS) in a PowerMac G5 11,2. The piglit
run completed all tests, the GPU resetted itself successfully after some
several crashes during the tests.
Simple 3D games (e.g extreme tuxracer) run without glitches.
piglit was built from current git-master.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=105256
Bug ID: 105256
Summary: Slow performance using glDrawElementsBaseVertex
Product: Mesa
Version: 17.3
Hardware: Other
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: logan(a)bacoosta.com
QA Contact: dri-devel(a)lists.freedesktop.org
Original application bug report here:
https://github.com/gonetz/GLideN64/issues/1561
This bug happens using mupen64plus (N64 emulator) and the GLideN64 graphics
plugin.
The application uses VBO streaming
(https://www.khronos.org/opengl/wiki/Buffer_Object_Streaming) using
ARB_buffer_storage to upload the VBO data.
Multiple users that when using Mesa + r600 driver, the performance was abysmal.
It turns out that converting the glDrawElementsBaseVertex calls to glDrawArrays
fixed the problem.
You can see the commit that fixed the problem here:
https://github.com/loganmc10/GLideN64/commit/9bcfa67d9550c7f1cd4ba72f657fac…
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=105227
Bug ID: 105227
Summary: [SUMO][TURKS] observer game cause GPU lockup
Product: Mesa
Version: git
Hardware: Other
OS: All
Status: NEW
Severity: critical
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 137557
--> https://bugs.freedesktop.org/attachment.cgi?id=137557&action=edit
dmesg from launch on Radeon HD 6650M
Hi!
Game "observer" cause GPU lockup on Radeon HD 6620G and 6650M GPUs with Mesa
18.1 4562a7b0e82bf664 - dmesg from two launch attempts is attached. Graphical
settings is all set to minimal, all visual effects is disabled.
[ 386.552620] radeon 0000:01:00.0: ring 0 stalled for more than 10288msec
[ 386.552638] radeon 0000:01:00.0: GPU lockup (current fence id
0x000000000000147b last fence id 0x0000000000001487 on ring 0)
[ 387.064666] radeon 0000:01:00.0: ring 0 stalled for more than 10800msec
[ 387.064683] radeon 0000:01:00.0: GPU lockup (current fence id
0x000000000000147b last fence id 0x0000000000001487 on ring 0)
[ 387.416749] radeon 0000:01:00.0: ring 3 stalled for more than 10036msec
[ 387.416765] radeon 0000:01:00.0: GPU lockup (current fence id
0x0000000000001001 last fence id 0x0000000000001002 on ring 3)
[ 387.576741] radeon 0000:01:00.0: ring 0 stalled for more than 11312msec
[ 387.576758] radeon 0000:01:00.0: GPU lockup (current fence id
0x000000000000147b last fence id 0x0000000000001487 on ring 0)
[ 387.928798] radeon 0000:01:00.0: ring 3 stalled for more than 10548msec
[ 387.928814] radeon 0000:01:00.0: GPU lockup (current fence id
0x0000000000001001 last fence id 0x0000000000001002 on ring 3)
To reproduce GPU lockup:
1. Launch game like this: MESA_GL_VERSION_OVERRIDE=4.3
MESA_GLSL_VERSION_OVERRIDE=430 %command% (otherwise it crash before launch)
2. Select New game, wait until loading completed.
3. After loading completed press space or left mouse button.
Hardware:
Acer Aspire 7560G, AMD A8-3500M
AMD Radeon HD 6620G iGPU, AMD Radeon HD 6650M dGPU.
Software:
Kubuntu 17.10 x86_64, Linux 4.15.5, Mesa 18.1 4562a7b0e82bf664
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=105095
Bug ID: 105095
Summary: piglit arb_vertex_type_2_10_10_10_rev-array_types
failed for BARTS
Product: Mesa
Version: 17.3
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: benau2006(a)yahoo.com.hk
QA Contact: dri-devel(a)lists.freedesktop.org
Output of arb_vertex_type_2_10_10_10_rev-array_types from piglit tests:
testing: RGBA SINT
testing: RGBA SNORM
Probe color at (25,5)
Expected: 0.500000 0.250000 0.000000 1.000000
Observed: 0.501961 0.250980 0.000000 0.333333
testing: RGBA UINT
testing: RGBA UNORM
testing: BGRA SNORM
Probe color at (85,5)
Expected: 0.000000 0.250000 0.500000 1.000000
Observed: 0.000000 0.250980 0.501961 0.333333
testing: BGRA UNORM
Mesa version 17.3.3
AMD/ATI Barts PRO Radeon HD 6850
Detail in https://github.com/supertuxkart/stk-code/issues/3097, this bug cause
wrong animation in stk.
And i think 2.2 / 2.3 equation isn't causing this bug, because from what i see
zero is represented correctly in stk, also some amd devs told me barts switched
to use the new formula long time ago.
Any idea?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=104831
Bug ID: 104831
Summary: CAYMAN:KDE applications SIGSEGV
Product: Mesa
Version: git
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
Created attachment 137016
--> https://bugs.freedesktop.org/attachment.cgi?id=137016&action=edit
kmail backtrace
testing mesa 18.0-rc2, Radeon HD6950
many KDE applications crash with the following in the backtrace.
I have seen this with ksplashqml, kmail, krunner and possibly plasma (but for
some reason symbols there get truncated).
Relevant (r600g) part of backtrace
Thread 1 (Thread 0x7f303aec5640 (LWP 4710)):
[KCrash Handler]
#6 0x00007f306fc84000 in __memcpy_ssse3 () from /lib64/libc.so.6
#7 0x00007f30338255b4 in tgsi_dup_tokens () from /usr/lib64/dri/r600_dri.so
#8 0x00007f303395fa9b in r600_create_shader_state_tokens () from
/usr/lib64/dri/r600_dri.so
#9 0x00007f303395fad3 in r600_create_shader_state () from
/usr/lib64/dri/r600_dri.so
#10 0x00007f3033674ecd in st_create_fp_variant () from
/usr/lib64/dri/r600_dri.so
#11 0x00007f3033676e56 in st_get_fp_variant () from /usr/lib64/dri/r600_dri.so
#12 0x00007f303362d070 in st_update_fp () from /usr/lib64/dri/r600_dri.so
#13 0x00007f303362968e in st_validate_state () from /usr/lib64/dri/r600_dri.so
#14 0x00007f3033647306 in st_draw_vbo () from /usr/lib64/dri/r600_dri.so
#15 0x00007f303360a108 in vbo_validated_drawrangeelements () from
/usr/lib64/dri/r600_dri.so
#16 0x00007f303360a89f in vbo_exec_DrawElements () from
/usr/lib64/dri/r600_dri.so
#17 0x00007f3062207551 in
QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*)
() from /usr/lib64/libQt5Quick.so.5
#18 0x00007f3062208935 in QSGBatchRenderer::Renderer::renderBatches() () from
/usr/lib64/libQt5Quick.so.5
--
You are receiving this mail because:
You are the assignee for the bug.