dri-devel January 2016

dri-devel@lists.freedesktop.org

194 participants
1200 discussions

[Bug 65327] New: running gnubik produces a segfault
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=65327 Priority: medium Bug ID: 65327 Assignee: dri-devel(a)lists.freedesktop.org Summary: running gnubik produces a segfault Severity: normal Classification: Unclassified OS: Linux (All) Reporter: pinode(a)gmail.com Hardware: x86 (IA32) Status: NEW Version: unspecified Component: DRM/Radeon Product: DRI Created attachment 80263 --> https://bugs.freedesktop.org/attachment.cgi?id=80263&action=edit bt full X.Org X Server 1.13.3 Fedora release 18 (Spherical Cow) bash-4.2$ lspci -v|grep ATI 02:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RV350 AP [Radeon 9600] (prog-if 00 [VGA controller]) 02:00.1 Display controller: Advanced Micro Devices [AMD] nee ATI RV350 AP [Radeon 9600] (Secondary) When I run gnubik (a game), the program segfaults immediately: bash-4.2$ gnubik Segmentation fault (core dumped) bash-4.2$ dmesg|tail -n 1 [ 5769.578454] gnubik[7155]: segfault at 0 ip (null) sp bfafcbbc error 4 in gnubik[8048000+16000] bash-4.2$ rpm -q gnubik gnubik-2.4-5.fc18.i686 bash-4.2$ gnubik -v|head -n 1 2.4 #0 0x00000000 in ?? () #1 0xb217e6f4 in generic_run () from /usr/lib/dri/r300_dri.so #2 0xb214ae9c in draw_pt_fetch_run_linear () from /usr/lib/dri/r300_dri.so it segfaults on line 646 (gdb) l translate/translate_generic.c:646 641 copy_size = tg->attrib[attr].copy_size; 642 if(likely(copy_size >= 0)) 643 memcpy(dst, src, copy_size); 644 else 645 { 646 tg->attrib[attr].fetch( data, src, 0, 0 ); 647 648 if (0) 649 debug_printf("Fetch linear attr %d from %p stride %d index %d: " 650 " %f, %f, %f, %f \n", (gdb) the bugtrace is attached Should any additional info be required, I may provide it. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 62578] New: r300: Implementation error: Render targets are too big in r300_set_framebuffer_state, refusing to bind framebuffer state!
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=62578 Priority: medium Bug ID: 62578 Assignee: dri-devel(a)lists.freedesktop.org Summary: r300: Implementation error: Render targets are too big in r300_set_framebuffer_state, refusing to bind framebuffer state! Severity: major Classification: Unclassified OS: All Reporter: orion(a)cora.nwra.com Hardware: x86 (IA32) Status: NEW Version: 9.1 Component: Drivers/DRI/r300 Product: Mesa Created attachment 76846 --> https://bugs.freedesktop.org/attachment.cgi?id=76846&action=edit Xorg.0.log Running KDE 4.10.1 on Fedora 18. After login, screen flickers a bit but nothing is displayed other than the background image. .xsession-errors contains: OpenGL vendor string: X.Org R300 Project OpenGL renderer string: Gallium 0.4 on ATI RV370 OpenGL version string: 2.1 Mesa 9.1 OpenGL shading language version string: 1.20 Driver: R300G GPU class: R300 OpenGL version: 2.1 GLSL version: 1.20 Mesa version: 9.1 Linux kernel version: 3.8.3 Direct rendering: yes Requires strict binding: yes GLSL shaders: limited Texture NPOT support: limited Virtual Machine: no r300: Implementation error: Render targets are too big in r300_set_framebuffer_state, refusing to bind framebuffer state! this r300 messages keeps repeating. kernel 3.8.3-203.fc18.i686.PAE 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RV370 5B60 [Radeon X300 (PCIE)] Just updated from Fedora 16 where this system was working fine. -- You are receiving this mail because: You are the assignee for the bug.

1 10

[Bug 61883] New: wine shader_generate_glsl_declarations fail
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=61883 Priority: medium Bug ID: 61883 Assignee: dri-devel(a)lists.freedesktop.org Summary: wine shader_generate_glsl_declarations fail Severity: normal Classification: Unclassified OS: Linux (All) Reporter: victoraur.santos(a)gmail.com Hardware: All Status: NEW Version: 9.1 Component: Drivers/DRI/r300 Product: Mesa Trying to run RE4 on my r300 freeze completely system Submitted on wine bug tracker and suggested to report here. ---- err:winediag:shader_generate_glsl_declarations The hardware does not support enough uniform components to run this shader, it may not render correctly. ---- and lot of: ---- r300: ERROR: FS input fog unassigned, not enough hardware slots. (it's not a bug, do not report it) ---- for more details and full log see: http://bugs.winehq.org/show_bug.cgi?id=33129 -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 60965] New: [r300g] Anno1701: flickering colorful corruption over some models
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=60965 Priority: medium Bug ID: 60965 Assignee: dri-devel(a)lists.freedesktop.org Summary: [r300g] Anno1701: flickering colorful corruption over some models Severity: normal Classification: Unclassified OS: All Reporter: pavel.ondracka(a)email.cz Hardware: Other Status: NEW Version: git Component: Drivers/Gallium/r300 Product: Mesa Created attachment 74949 --> https://bugs.freedesktop.org/attachment.cgi?id=74949&action=edit RADEON_DEBUG=fp,vp In Anno1701, there are flickering colorful spots over some models. It looks similar to the bug 60552, except the spots are colorful instead of black and they don't go away with RADEON_DEBUG=noopt. Setting Wine to use ARB shader rendering backend instead of GLSL makes the problem go away indicating another bug in the shader compiler. Apitrace here http://pavel.ondracka.cz/Anno1701.trace (renders fine with proprietary NVIDIA drivers). Wine: 1.5.23 GPU: RV530 Mesa: f1ab67c13ab97f19c08d99c6ba101edc7d7b80e6 Kernel: 3.7.3-101.fc17.i686 -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 60963] New: [r300g] Anno1701: some models are red
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=60963 Priority: medium Bug ID: 60963 Assignee: dri-devel(a)lists.freedesktop.org Summary: [r300g] Anno1701: some models are red Severity: normal Classification: Unclassified OS: All Reporter: pavel.ondracka(a)email.cz Hardware: Other Status: NEW Version: git Component: Drivers/Gallium/r300 Product: Mesa Created attachment 74948 --> https://bugs.freedesktop.org/attachment.cgi?id=74948&action=edit RADEON_DEBUG=fp,vp In Anno1701, some models are red, however they are rendered with correct colors when RADEON_DEBUG=noopt is used (or with glsl disabled in Wine). Apitrace here http://pavel.ondracka.cz/Anno1701.trace (renders fine with proprietary NVIDIA drivers). Wine: 1.5.23 GPU: RV530 Mesa: f1ab67c13ab97f19c08d99c6ba101edc7d7b80e6 Kernel: 3.7.3-101.fc17.i686 -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 60555] New: [r300g] RADEON_NO_TCL=1 hardlock
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=60555 Priority: lowest Bug ID: 60555 Assignee: dri-devel(a)lists.freedesktop.org Summary: [r300g] RADEON_NO_TCL=1 hardlock Severity: trivial Classification: Unclassified OS: All Reporter: pavel.ondracka(a)email.cz Hardware: Other Status: NEW Version: git Component: Drivers/DRI/r300 Product: Mesa This is not really a bug as normal user will never encounter this, just some nuisance I discovered when I tried to investigate bug 60552 a little bit. When RADEON_NO_TCL=1 is used (which is useful in diagnosing compiler bugs), the whole machine sometimes hardlocks. App from bug 60552 is a good way to reproduce this. This debug option should be either fixed, or if it no longer considered useful, then it should be removed. BTW this was working not a year ago, so I can probably run a bisect if needed. -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 60552] New: [r300g] Carvisualizer webgl demo: black flickering spots over the car
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=60552 Priority: medium Bug ID: 60552 Assignee: dri-devel(a)lists.freedesktop.org Summary: [r300g] Carvisualizer webgl demo: black flickering spots over the car Severity: normal Classification: Unclassified OS: All Reporter: pavel.ondracka(a)email.cz URL: http://carvisualizer.plus360degrees.com/threejs/ Hardware: Other Status: NEW Version: git Component: Drivers/Gallium/r300 Product: Mesa Created attachment 74497 --> https://bugs.freedesktop.org/attachment.cgi?id=74497&action=edit screenshot In the Car Visualizer Webgl demo, there are some flickering black spots on the car. This is probably a bug in the shader compiler, as RADEON_DEBUG=noopt works around this. Specifically its the register_rename pass that causes this, when it is disabled in r3xx_fragprog.c, everything is fine. Also when I disable only the dataflow optimize pass, there is still some flickering but much less. Firefox 18.0 GPU:RV530 Mesa: 0e2f26d5ea26febd16173aa8bbf7427b090e320f Kernel: 3.7.3-101.fc17.i686 -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 59899] New: Diagonal rendering artifacts on xbmc
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=59899 Priority: medium Bug ID: 59899 Assignee: dri-devel(a)lists.freedesktop.org Summary: Diagonal rendering artifacts on xbmc Severity: normal Classification: Unclassified OS: Linux (All) Reporter: aeriksson(a)fastmail.fm Hardware: x86-64 (AMD64) Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI Hi, Just moved to xbmc (which uses gl), from freevo and more often than not, I get extreme diagonal rendering artifacts on the gui. Pretty much each gui object (a box, a single character, etc) has a diagonal split and either of the halves renders o, and the other is mostly black. The diagonal flickers between the corners at a rapid pase (~ 4 changes / second). I files report on it at xbmc (http://trac.xbmc.org/ticket/14017) which also has screenshots and a short movie grab attached. Freevo worked ok, so I guess this is somehow related to new code paths executed by xbmc (both 11.0 and 12-git suffers). I have no idea if it's kernel driver related or somewhere higher in the stack. Ideas to narrow this down appreciated. xbmc is the only app which behaves like this. -ath -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 59172] New: [r300g] flashing and corruption with MSAA 6x and 1920x1080
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=59172 Priority: medium Bug ID: 59172 Assignee: dri-devel(a)lists.freedesktop.org Summary: [r300g] flashing and corruption with MSAA 6x and 1920x1080 Severity: normal Classification: Unclassified OS: Linux (All) Reporter: fabio.ped(a)libero.it Hardware: x86 (IA32) Status: NEW Version: git Component: Drivers/Gallium/r300 Product: Mesa When running some applications such as supertuxkart 0.8 with a high resolution (1920x1080) and MSAA 6x the screen flashes, shows massive corruptions and gets very slow. Just changing MSAA to 4x the problem is no longer reproducible. Tested on current git with: r300: DRM version: 2.18.0, Name: ATI RV530, ID: 0x71c5, GB: 1, Z: 2 r300: GART size: 509 MB, VRAM size: 256 MB r300: AA compression RAM: YES, Z compression RAM: YES, HiZ RAM: YES -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 58131] New: r300g: Corruption in Half Life 2 unless gl_ClipVertex is written
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=58131 Priority: medium Bug ID: 58131 Assignee: dri-devel(a)lists.freedesktop.org Summary: r300g: Corruption in Half Life 2 unless gl_ClipVertex is written Severity: normal Classification: Unclassified OS: All Reporter: stefandoesinger(a)gmx.at Hardware: Other Status: NEW Version: git Component: Drivers/Gallium/r300 Product: Mesa Created attachment 71330 --> https://bugs.freedesktop.org/attachment.cgi?id=71330&action=edit Screenshot of the static main menu Half-Life 2 (running in Wine) has a random vertex corruption. This corruption can be seen in the static main menu(start it with -console) and in-game. The corruption goes away if I modify Wine to always write gl_ClipVertex even if clipping is disabled. This is interesting particularly because r300g does not support clipping with vertex shaders. It says so on the command line, and in-game rendering and the Wine tests confirm this. -- You are receiving this mail because: You are the assignee for the bug.

1 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel January 2016