dri-devel June 2015

dri-devel@lists.freedesktop.org

188 participants
1140 discussions

[Bug 66632] New: Very low FPS when video memory is full (GART & ram <-> vram swapping)
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=66632 Priority: medium Bug ID: 66632 Assignee: dri-devel(a)lists.freedesktop.org Summary: Very low FPS when video memory is full (GART & ram <-> vram swapping) Severity: major Classification: Unclassified OS: Linux (All) Reporter: sonichedgehog_hyperblast00(a)yahoo.com Hardware: All Status: NEW Version: 7.0 Component: Drivers/DRI/Radeon Product: Mesa Although I heard this issue was discussed, I couldn't find other bug reports and wanted to post my observations on the matter. At this point it's the only reason why I'm sticking with fglrx and can't switch to Radeon, and so far couldn't find a workaround either. Although Radeon and fglrx seem to run games as fast when no bugs occur, Radeon has a major problem. If video memory is filled and textures have to be stored on system memory, FPS drops unusably low. This can be noticed when a program uses high quality content such as a lot of high resolution textures, enough to fill up the video memory. The best and only test case I know of (also the reason this problem affects me) is the project Xonotic. When ran from the GIT repository, it has a lot of high-res textures in original format (some as large as 2048px). Even when texture compression is enabled, they quickly fill up my 1GB of video ram. Therefore, when looking in certain areas of a map, FPS decreases enormously (down to 3 FPS). I ran several tests in the past and tried further debugging this today on IRC. As other users pointed out, the constant swapping of items between the RAM and VRAM is the most likely cause of the problem. A better GART formula is apparently needed in order to swap only when necessary and not all the time. Someone posted a log based on their tests: http://bpaste.net/raw/lhJKFAYFyl0DNOMr9hwc/ At least one more user could replicate the exact behavior I'm getting, and confirmed Xonotic is unplayable when full-res textures are used and a map loads a lot of them. I was also linked a patch, which was said to fix the issue although it wasn't accepted yet. In case it's of any relevance, http://people.freedesktop.org/~glisse/0001-drm-radeon-keep-original-user-re… I heard a correct formula on when to trigger VRAM <-> RAM swapping is harder to find, so I understand why this bug exists. Since it's a major issue and keeps some engines from working when they could, it would be appreciated if even a simple solution could be added in the meantime. Such as disabling swapping altogether (what was placed in vram stays in vram and what's in gart stays in gart) or only triggering swapping after a longer amount of time rather than each frame (eg: 30 or 60 seconds). -- You are receiving this mail because: You are the assignee for the bug.

1 13

[Bug 66349] New: Using SB shader optimization caused segfault in Serious Sam 3: BFE
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=66349 Priority: medium Bug ID: 66349 Assignee: dri-devel(a)lists.freedesktop.org Summary: Using SB shader optimization caused segfault in Serious Sam 3: BFE Severity: normal Classification: Unclassified OS: Linux (All) Reporter: thomas.lindroth(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/Gallium/r600 Product: Mesa Created attachment 81666 --> https://bugs.freedesktop.org/attachment.cgi?id=81666&action=edit dmesg, xorg.log When using R600_DEBUG=sb Serious Sam 3 will segfault in mesa during the intro. Running without sb works. I'm using git mesa, libdrm, drm-next and xf86-video-ati-7.1.0. Here is the backtrace. Program received signal SIGSEGV, Segmentation fault. 0xf385b151 in r600_sb::regbits::clear (this=0xffe4b57c, index=4293178748) at sb/sb_ra_init.cpp:131 131 sb/sb_ra_init.cpp: No such file or directory. (gdb) bt #0 0xf385b151 in r600_sb::regbits::clear (this=0xffe4b57c, index=4293178748) at sb/sb_ra_init.cpp:131 #1 0xf385b25b in r600_sb::regbits::from_val_set (this=0xffe4b57c, sh=..., vs=...) at sb/sb_ra_init.cpp:117 #2 0xf385bdaa in regbits (vs=..., sh=..., this=0xffe4b57c) at sb/sb_ra_init.cpp:62 #3 r600_sb::ra_init::color (this=0xffe4bb18, v=0x15c62168) at sb/sb_ra_init.cpp:471 #4 0xf385bf81 in r600_sb::ra_init::process_op (this=0xffe4bb18, n=0x15ca7948) at sb/sb_ra_init.cpp:344 #5 0xf385bfdf in r600_sb::ra_init::ra_node (this=0xffe4bb18, c=0x15cba670) at sb/sb_ra_init.cpp:294 #6 0xf385bff7 in r600_sb::ra_init::ra_node (this=0xffe4bb18, c=0x15cba608) at sb/sb_ra_init.cpp:297 #7 0xf385bff7 in r600_sb::ra_init::ra_node (this=0xffe4bb18, c=0x15c8a4e8) at sb/sb_ra_init.cpp:297 #8 0xf385c03d in r600_sb::ra_init::run (this=0xffe4bb18) at sb/sb_ra_init.cpp:285 #9 0xf3847450 in r600_sb_bytecode_process (rctx=0xa60a300, bc=0x15c6c9f4, pshader=0x15c6c9f0, dump_bytecode=0, optimize=2097152) at sb/sb_core.cpp:220 #10 0xf38209f8 in r600_pipe_shader_create (ctx=0xa60a300, shader=0x15c6c9e8, key=...) at r600_shader.c:179 #11 0xf38335b1 in r600_shader_select (ctx=0xa60a300, sel=<optimized out>, dirty=0x0) at r600_state_common.c:750 #12 0xf38337ea in r600_create_shader_state (ctx=0xa60a300, state=<optimized out>, pipe_shader_type=1) at r600_state_common.c:797 #13 0xf3833834 in r600_create_ps_state (ctx=0xa60a300, state=0x15c43c28) at r600_state_common.c:807 #14 0xf365f051 in st_translate_fragment_program (st=0xa73f748, stfp=0x15c7a060, key=0xffe4c648) at ../../src/mesa/state_tracker/st_program.c:768 #15 0xf365fd20 in st_get_fp_variant (st=0xa73f748, stfp=0x15c7a060, key=0xffe4c648) at ../../src/mesa/state_tracker/st_program.c:805 #16 0xf3626b85 in update_fp (st=0xa73f748) at ../../src/mesa/state_tracker/st_atom_shader.c:92 #17 0xf3623912 in st_validate_state (st=0xa73f748) at ../../src/mesa/state_tracker/st_atom.c:221 #18 0xf36376fc in st_draw_vbo (ctx=0xa6f8b28, prims=0xffe4c7d8, nr_prims=1, ib=0xffe4c7f0, index_bounds_valid=1 '\001', min_index=0, max_index=3, tfb_vertcount=0x0) at ../../src/mesa/state_tracker/st_draw.c:210 #19 0xf360da07 in vbo_handle_primitive_restart (ctx=<optimized out>, prim=<optimized out>, nr_prims=1, ib=0xffe4c7f0, index_bounds_valid=1 '\001', min_index=0, max_index=3) at ../../src/mesa/vbo/vbo_exec_array.c:549 #20 0xf360e8ec in vbo_validated_drawrangeelements (ctx=0xa6f8b28, mode=4, index_bounds_valid=1 '\001', start=0, end=3, count=6, type=5123, indices=0x0, basevertex=0, numInstances=1, baseInstance=0) at ../../src/mesa/vbo/vbo_exec_array.c:968 #21 0xf360eaa7 in vbo_exec_DrawRangeElementsBaseVertex (mode=4, start=0, end=3, count=6, type=5123, indices=0x0, basevertex=0) at ../../src/mesa/vbo/vbo_exec_array.c:1076 #22 0xf360eaeb in vbo_exec_DrawRangeElements (mode=4, start=0, end=3, count=6, type=5123, indices=0x0) at ../../src/mesa/vbo/vbo_exec_array.c:1096 #23 0x08f0bf3d in ?? () #24 0x08a9f8b1 in ?? () #25 0x089a8459 in ?? () #26 0x089a188e in ?? () #27 0x08aadc5a in ?? () #28 0x08a9fb0a in ?? () #29 0x08a9fd56 in ?? () #30 0x08c8e65f in ?? () #31 0x08c9284a in ?? () #32 0x08b52309 in ?? () #33 0x08b66e96 in ?? () #34 0x08b92394 in ?? () ---Type <return> to continue, or q <return> to quit--- #35 0x08b498de in ?? () #36 0x08b49a86 in ?? () #37 0x08b49be1 in ?? () #38 0x08d89685 in ?? () #39 0x08b4a23d in ?? () #40 0x08b45e77 in ?? () #41 0x08b47332 in ?? () #42 0x0888e7fa in ?? () #43 0x0888867e in ?? () #44 0x083e9df5 in ?? () #45 0x083ea964 in ?? () #46 0x0853f143 in ?? () #47 0x089143d0 in ?? () #48 0x083a017f in ?? () #49 0x083a0293 in ?? () #50 0x08a06046 in ?? () #51 0x08d85243 in ?? () #52 0x08d85678 in ?? () #53 0x0804f54b in ?? () #54 0xf755a943 in __libc_start_main (main=0x804f520, argc=1, ubp_av=0xffe4e114, init=0x8f63330, fini=0x8f633a0, rtld_fini=0xf77964e0 <_dl_fini>, stack_end=0xffe4e10c) at libc-start.c:226 #55 0x0838e785 in ?? () -- You are receiving this mail because: You are the assignee for the bug.

1 10

[Bug 66067] New: Trine 2 color problems on Radeon HD 6770 (Juniper)
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=66067 Priority: medium Bug ID: 66067 Assignee: dri-devel(a)lists.freedesktop.org Summary: Trine 2 color problems on Radeon HD 6770 (Juniper) Severity: normal Classification: Unclassified OS: All Reporter: nmiell(a)gmail.com Hardware: Other Status: NEW Version: git Component: Drivers/DRI/R600 Product: Mesa Created attachment 81244 --> https://bugs.freedesktop.org/attachment.cgi?id=81244&action=edit rendering with Mesa d282f4ea9b99e4eefec8ce0664cdf49d53d7b052 Trine 2 colors/lighting are wrong with Mesa 9.2 and current git (d282f4ea9b99e4eefec8ce0664cdf49d53d7b052) on a Radeon HD 6770 Juniper XT. Game renders correctly using the Catalyst drivers. Colors are wrong enough to make some puzzles unsolvable because portions of the screen are too dark to see. Sample apitrace is at https://docs.google.com/file/d/0B8G3Ivdx_-JNTV96YjgyNWplZ0U/edit?usp=sharing Attached screenshots were generated using glretrace -b -S 5670984 -- You are receiving this mail because: You are the assignee for the bug.

1 44

[Bug 65611] New: UVD accelerated decoding causes hangs (ARUBA - HD 7540D)
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=65611 Priority: medium Bug ID: 65611 Assignee: dri-devel(a)lists.freedesktop.org Summary: UVD accelerated decoding causes hangs (ARUBA - HD 7540D) Severity: normal Classification: Unclassified OS: Linux (All) Reporter: otaznik(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/Gallium/r600 Product: Mesa Created attachment 80626 --> https://bugs.freedesktop.org/attachment.cgi?id=80626&action=edit relevant dmesg output New UVD VDPAU decoding of VC-1 and MPEG-2 causes some kind of corruption and ultimately hang of driver and whole system on the next try (cursor can be moving for some time, even SysRq can work a few seconds after X totally hangs but then only power off works). Few notes (using mplayer): ffmpeg12vdpau: MPEG1 causes no harm, only decoding is really bad (software decoding works) MPEG2 seems to cause really bad corruption ffvc1vdpau: VC-1 seems to cause problems (like attached dmesg) but not hangs. There have been decoding artifacts too, but it is not the rule. divx and h264 seems to work flawless, unless previous corruption happened. Hardware is ARUBA - A6-5400K Black Edition APU (Radeon HD 7540D). Since this particular hardware seems to be problematic (#65254 #60389) it might be unique to this APU. Test files: VC1 http://samples.mplayerhq.hu/V-codecs/WVC1/Test_1440x576_WVC1_6Mbps.wmv MPEG2 http://samples.mplayerhq.hu/MPEG2/vid_0x80.ts MPEG1 http://samples.mplayerhq.hu/MPEG1/ -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 65448] New: Driver fails to compile complex shaders
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=65448 Priority: medium Bug ID: 65448 Assignee: dri-devel(a)lists.freedesktop.org Summary: Driver fails to compile complex shaders Severity: normal Classification: Unclassified OS: Linux (All) Reporter: greg(a)chown.ath.cx Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/Gallium/r600 Product: Mesa The r600 driver fails to translate TGSI to bytecode for complex shaders. https://www.shadertoy.com/view/MdX3Rr is an example for this. The fragment shader compiles into a pretty big TGSI program (about 6500 instructions). r600 takes a long time (tens of seconds) trying to transform it into bytecode, but in then end it fails: EE ../../../../../mesa/src/gallium/drivers/r600/r600_shader.c:158 r600_pipe_shader_create - translation from TGSI failed ! EE ../../../../../mesa/src/gallium/drivers/r600/r600_state_common.c:753 r600_shader_select - Failed to build shader variant (type=1) -1 This happens with many of the shaders from shadertoy.com. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 65316] New: [r600g] Game window turns completely black occasionally in WoW.
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=65316 Priority: medium Bug ID: 65316 Assignee: dri-devel(a)lists.freedesktop.org Summary: [r600g] Game window turns completely black occasionally in WoW. Severity: normal Classification: Unclassified OS: Linux (All) Reporter: rankincj(a)googlemail.com Hardware: x86 (IA32) Status: NEW Version: git Component: Drivers/Gallium/r600 Product: Mesa When playing WoW in 32 bit mode, the game window occasionally turns completely black for a second or two before correctly redrawing itself. However, the UI elements remain visible throughout. I have reproduced this problem with a RV730XT card (HD4670 AGP) and a CAICOS HD6450, but not with my RV790. Note that the HD4670 AGP can only run in 32 bit mode, but the CAICOS runs WoW correctly in 64 bit mode. This is not a new problem (at all!), but I have only recently discovered that it happens with my CAICOS card in 32 bit mode while I was investigating a bug with the sound. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 64819] New: GPU fault detected flood at A8-5600K Trinity 7560D
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=64819 Priority: medium Bug ID: 64819 Assignee: dri-devel(a)lists.freedesktop.org Summary: GPU fault detected flood at A8-5600K Trinity 7560D Severity: normal Classification: Unclassified OS: Linux (All) Reporter: p00hzone(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/DRI/Radeon Product: Mesa Created attachment 79612 --> https://bugs.freedesktop.org/attachment.cgi?id=79612&action=edit dmesg.log I have exactly similar bug as described at https://bugs.freedesktop.org/show_bug.cgi?id=59089 with Trinity 7560D at A8-5600K. I'm using latest git drivers. As that bug marked as fixed should i claim that my problem is unrelated and caused by hardware and/or other malfunctions? My problem consists of NOT log flood only, but the whole machine usually freezes and nothing except hard reboot can fix this. Problem detects in both idle and high load mode. The temperature of APU is about 20-40C. #uname -a Linux multiseat 3.9.2-1-gpgpu #lspci | grep VGA 00:01.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Trinity [Radeon HD 7560D] -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 64649] New: [r600g] Anomaly 2 (Steam) crashes with GLX_EXT_swap_control not supported, unable to set vertical sync
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=64649 Priority: medium Bug ID: 64649 Assignee: dri-devel(a)lists.freedesktop.org Summary: [r600g] Anomaly 2 (Steam) crashes with GLX_EXT_swap_control not supported, unable to set vertical sync Severity: critical Classification: Unclassified OS: Linux (All) Reporter: romulasry(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/Gallium/r600 Product: Mesa Game update: AppID 236730 "Anomaly 2", ProcID 7610, IP 0.0.0.0:0 ERROR: ld.so: object 'gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded: ignored. GLX_EXT_swap_control not supported, unable to set vertical sync. -- You are receiving this mail because: You are the assignee for the bug.

1 13

[Bug 64508] New: Text rendered using QuesoGLC is unreadable/missing on Radeon HD 6290
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=64508 Priority: medium Bug ID: 64508 Assignee: dri-devel(a)lists.freedesktop.org Summary: Text rendered using QuesoGLC is unreadable/missing on Radeon HD 6290 Severity: normal Classification: Unclassified OS: Linux (All) Reporter: maxrd2(a)hotmail.com Hardware: x86-64 (AMD64) Status: NEW Version: 9.1 Component: Drivers/DRI/R600 Product: Mesa Created attachment 79212 --> https://bugs.freedesktop.org/attachment.cgi?id=79212&action=edit screenshots in order: test9.1, test9.2, test16 Overview: Text rendered using QuesoGLC is unreadable/missing on Radeon HD 6290. As a consequence all text in warzone2100 game is unreadable. Steps to Reproduce: wget http://surfnet.dl.sourceforge.net/project/quesoglc/QuesoGLC/0.7.2/quesoglc-… tar -xjf quesoglc-0.7.2.tar.bz2 ./configure && make check Actual Results: Following tests look very bad... letters look like a bunch of overlapping triangles/primitives (attached screenshots) - test9.2 - Render style : GLC_TEXTURE without GL objects without user list - test16 Expected Results: Normally rendered text Platform: Arch Linux x86_64 Kernel: 3.8.12-1-ck #1 SMP PREEMPT x86_64 GNU/Linux mesa 9.1.2-1 ati-dri 9.1.2-1 glu 9.0.0-2 xorg-server 1.14.1-1 xf86-video-ati 1:7.1.0-3 lspci output: 00:01.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Wrestler [Radeon HD 6290] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device 0598 Flags: bus master, fast devsel, latency 0, IRQ 41 Memory at e0000000 (32-bit, prefetchable) [size=256M] I/O ports at 4000 [size=256] Memory at f0400000 (32-bit, non-prefetchable) [size=256K] Expansion ROM at <unassigned> [disabled] Capabilities: <access denied> Kernel driver in use: radeon Kernel modules: radeon -- You are receiving this mail because: You are the assignee for the bug.

1 12

[Bug 64225] New: bfgminer --scyte generates Segmentation Fault on Northern Island
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=64225 Priority: medium Bug ID: 64225 Assignee: dri-devel(a)lists.freedesktop.org Summary: bfgminer --scyte generates Segmentation Fault on Northern Island Severity: normal Classification: Unclassified OS: Linux (All) Reporter: spamjunkeater(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/DRI/R600 Product: Mesa Created attachment 78869 --> https://bugs.freedesktop.org/attachment.cgi?id=78869&action=edit ./bfgminer -v1 --benchmark --scrypt &> OpenSUSE LLVM-trunk (patched version using: https://bugs.freedesktop.org/attachment.cgi?id=78831) with Mesa trunk 3.9 kernel x86_64 "./bfgminer -v1 --benchmark --scrypt" Generated segmentation fault. Log attached. Thanks -- You are receiving this mail because: You are the assignee for the bug.

1 15

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel June 2015