dri-devel September 2019

dri-devel@lists.freedesktop.org

315 participants
2278 discussions

[Bug 86130] Some textures are not rendering correctly in apitrace but are fine while capturing
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=86130 Bug ID: 86130 Summary: Some textures are not rendering correctly in apitrace but are fine while capturing Product: Mesa Version: git Hardware: All OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 Assignee: dri-devel(a)lists.freedesktop.org Reporter: b.bellec(a)gmail.com Created attachment 109249 --> https://bugs.freedesktop.org/attachment.cgi?id=109249&action=edit Example of a broken weapon texture I captured a Serious Sam 3 trace with apitrace. The game is correctly rendered when capturing. But when retracing with qapitrace, most of the time the weapons textures are completely broken, see the screenshot in attachment for a preview. I posted this issue on the apitrace mailing list, where José Fonseca give me some advice and provided some patch I tested, but no patch or tips were able to solve the problem. My discussion with José has many details, you should look here : http://lists.freedesktop.org/archives/apitrace/2014-November/001011.html I have this issue with a Radeon HD5850 (CYPRESS) and a HD4850 (RV770) too. But not with a GeForce GT210 (NVA8). I have no other card to test. I'm currently using Mesa 10.3.2 but also tested with 9.0 without better results. I provided several (api)trace to José on the mailing list, you could find them on the thread pointed above. I'm available for more details or test. -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 85613] New: still getting segfault with vdpau and r600g on Radeon 3850HD - have sample video
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=85613 Bug ID: 85613 Summary: still getting segfault with vdpau and r600g on Radeon 3850HD - have sample video Product: Mesa Version: unspecified 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: arthur.marsh(a)internode.on.net I have a video sample online that still gives me a segfault when playing back under vlc. It plays back fine under mpv and mplayer using vdpau. Debian bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766058 VLC bug report: https://trac.videolan.org/vlc/ticket/12644 VLC have closed the bug on their side claiming that it's a vdpau driver issue. video sample: http://www.users.on.net/~arthur.marsh/VTS_01_1.VOB (152 Megabytes) I'm using vlc 2.2.0~pre4-2 on Debian unstable with mesa 10.3.2-1 using a Radeon 3850HD card and am happy to run further tests and rebuild mesa with patches. Arthur. -- You are receiving this mail because: You are the assignee for the bug.

1 15

[Bug 85596] New: SB is used only after GPR check / GPR max is not dynamic
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=85596 Bug ID: 85596 Summary: SB is used only after GPR check / GPR max is not dynamic 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: curaga(a)operamail.com Many big shaders that currently fail with r600_shader_select - Failed to build shader variant (type=1) -12 r600_shader_from_tgsi - GPR limit exceeded - shader requires foo registers would actually work if the GPR check was moved to after SB, as SB reduces the GPR usage quite nicely. Another thing is that 128 is the lowest common denominator, and many cards have 192 or 256, which could be checked with the radeon_info ioctl. -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 84920] New: Radeon UVD error
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=84920 Bug ID: 84920 Summary: Radeon UVD error Product: Mesa Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 Assignee: dri-devel(a)lists.freedesktop.org Reporter: barz621(a)gmail.com I had this on occasion but couldn't reproduce it reliably: Go to: http://global.burton.com/on/demandware.store/Sites-Burton_GLOBAL-Site/defau… and move the cursor over the faces. You will see many (toooo many) errors like the one below in the journal: Oct 11 23:20:38 mainland kernel: [drm:radeon_uvd_cs_msg] *ERROR* No more free UVD handles! Oct 11 23:20:38 mainland kernel: [drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream ! Linux mainland 3.16.4-1-ARCH #1 SMP PREEMPT Mon Oct 6 08:22:27 CEST 2014 x86_64 GNU/Linux glxinfo | grep -i opengl OpenGL vendor string: X.Org OpenGL renderer string: Gallium 0.4 on AMD BARTS OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.3.0 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.0 Mesa 10.3.0 OpenGL shading language version string: 1.30 OpenGL context flags: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.0 Mesa 10.3.0 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.0 OpenGL ES profile extensions: The dmesg is useless cause the error filled everything. -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 84519] New: GPU hang xbmc tvheadend uvd
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=84519 Priority: medium Bug ID: 84519 Assignee: dri-devel(a)lists.freedesktop.org Summary: GPU hang xbmc tvheadend uvd Severity: normal Classification: Unclassified OS: All Reporter: serafean(a)gmail.com Hardware: Other Status: NEW Version: unspecified Component: Drivers/Gallium/r600 Product: Mesa Created attachment 107140 --> https://bugs.freedesktop.org/attachment.cgi?id=107140&action=edit dmesg from around the hang When playing back a live TV stream using xbmc and tvheadend I immediately get a GPU hang. relevant dmesg attached. 00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7480D] Anything more I could do, please tell me. -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 84292] New: Radeonsi crashes in Tropico 5 with Radeon HD 5xxx
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=84292 Priority: medium Bug ID: 84292 Assignee: dri-devel(a)lists.freedesktop.org Summary: Radeonsi crashes in Tropico 5 with Radeon HD 5xxx Severity: normal Classification: Unclassified OS: Linux (All) Reporter: armandos.styl(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: 10.2 Component: Drivers/Gallium/radeonsi Product: Mesa Created attachment 106807 --> https://bugs.freedesktop.org/attachment.cgi?id=106807&action=edit System information text doc Two users (one of them myself) have experienced trouble with Tropico 5. "Last patch made it run the menu but starting the new game renders the system unusable and requires a reboot :( Last message in the system log is this: kernel: radeon 0000:01:00.0: ring 0 stalled for more than 10000msec GPU is Mobility Radeon HD 5730 with mesa 10.2.8 drivers on kernel 3.16.3." (steam fora) And me: "Tried both Tropico 5 main and linuxbeta, on intel i7 CPU 930 and AMD Radeon HD 5870. Had to work around the black screen issue but, upon reaching the main menu and clicking on New Campaign or Tutorial, the screen would flash and glitch and sound would repeat. After that, my monitor would turn on and off and display Refresh rate out of range (approx. 43.1 KHz - 41 Hz) and the system would need a cold reboot. Tried to run it with both the updated kernel and without, realising I had never let it run for more than 30 seconds after the freeze. Result was that the fans inside my computer began spinning like crazy, the system restarted with 4-5 ping sounds and the fans still running full-speed. Only after a cold shutdown did the fans stop. So I suspect this process almost fried my CPU or GPU." I am running updated Mesa and Gallium through oibaf ppa. -- You are receiving this mail because: You are the assignee for the bug.

1 16

[Bug 83422] New: i was opening systemsettings, chose workspace design and the default look and feel screen just stays black when resizing the window or chosing another option on the left panel, it crashes
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=83422 Priority: medium Bug ID: 83422 Assignee: dri-devel(a)lists.freedesktop.org Summary: i was opening systemsettings, chose workspace design and the default look and feel screen just stays black when resizing the window or chosing another option on the left panel, it crashes Severity: normal Classification: Unclassified OS: Linux (All) Reporter: simonlang1984(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: unspecified Component: Drivers/Gallium/r600 Product: Mesa Created attachment 105657 --> https://bugs.freedesktop.org/attachment.cgi?id=105657&action=edit logfile i was opening systemsettings, chose workspace design and the default look and feel screen just stays black when resizing the window or chosing another option on the left panel, it crashes. could not reproduce the crash, but the black window thing remains. Reproducible: Always Steps to Reproduce: 1. open system settings 2. chose workspace design 3. see the problem Actual Results: i was opening systemsettings, chose workspace design and the default look and feel screen just stays black when resizing the window or chosing another option on the left panel, it crashes. could not reproduce the crash, but the black window thing remains. Expected Results: should not crash and should show the contents. http://s18.postimg.org/a460edqah/Bildschirmfoto1.png -- You are receiving this mail because: You are the assignee for the bug.

1 20

[Bug 83319] New: [r600g] GPU lockup in gsraytrace (Mesa-demo-8.2.0) - RV730
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=83319 Priority: medium Bug ID: 83319 Assignee: dri-devel(a)lists.freedesktop.org Summary: [r600g] GPU lockup in gsraytrace (Mesa-demo-8.2.0) - RV730 Severity: critical Classification: Unclassified OS: Linux (All) Reporter: Dieter(a)nuetzel-hh.de Hardware: x86 (IA32) Status: NEW Version: git Component: Drivers/Gallium/r600 Product: Mesa Created attachment 105518 --> https://bugs.freedesktop.org/attachment.cgi?id=105518&action=edit dmesg-3.16.1-7.g90bc0f1-desktop-gsraytrace.log GL_RENDERER = Gallium 0.4 on AMD RV730 GL_VERSION = 3.0 Mesa 10.4.0-devel (git-5598458) GL_VENDOR = X.Org GShader thing? mesa-demos/glsl> ./vsraytrace ATTENTION: default value of option vblank_mode overridden by environment. GL_RENDERER = Gallium 0.4 on AMD RV730 47.590482 FPS (238 frames in 5.001000 seconds) 62.325210 FPS (312 frames in 5.006000 seconds) 65.407555 FPS (329 frames in 5.030000 seconds) mesa-demos/glsl> ./fsraytrace ATTENTION: default value of option vblank_mode overridden by environment. GL_RENDERER = Gallium 0.4 on AMD RV730 503.000000 FPS (2515 frames in 5.000000 seconds) 626.800000 FPS (3134 frames in 5.000000 seconds) 577.600000 FPS (2888 frames in 5.000000 seconds) mesa-demos/glsl> ./gsraytrace ATTENTION: default value of option vblank_mode overridden by environment. GL_RENDERER = Gallium 0.4 on AMD RV730 ESC = exit demo left mouse + drag = rotate camera 0.044960 FPS (1 frames in 22.242000 seconds) 0.047201 FPS (1 frames in 21.186000 seconds) ESC / CNTRL+C (several/hundred times) => 2 times switching between blank (black) full screen (console) and desktop (KDE 4.13.3) before the system comes back NO, no LLVM this time... (Michel?) Maybe related: bug 76394 -- You are receiving this mail because: You are the assignee for the bug.

1 18

[Bug 83285] New: GPU Lockup using wine d3d
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=83285 Priority: medium Bug ID: 83285 Assignee: dri-devel(a)lists.freedesktop.org Summary: GPU Lockup using wine d3d Severity: blocker Classification: Unclassified OS: Linux (All) Reporter: josepwnz(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/Gallium/r600 Product: Mesa Created attachment 105479 --> https://bugs.freedesktop.org/attachment.cgi?id=105479&action=edit Kern.log Hi, im getting some gpu resets (sometimes even reboot computer) playing some games (League of legends & starcraft2) using wine (patched for d3d) I have to say it only happens using certain settings, for example using "character quality" option from league of legends setting to very low/low game loads normally. if i set to medium or higher then causes GPU reset loops untill game crash/computer completly freeze(need reboot)/or if i'm enough faster, kill process from tty. If you need, i can try to make a movie showing problem Linux mint 17 Kernel 3.16.0 OpenGL ES 3.0 Mesa 10.4.0-devel (git-932b0ef 2014-08-30 trusty-oibaf-ppa) ATI 6670 -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 83274] New: XCom Enemy Unknown segfault at src/gallium/drivers/radeon/r600_texture.c:602
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=83274 Priority: medium Bug ID: 83274 Assignee: dri-devel(a)lists.freedesktop.org Summary: XCom Enemy Unknown segfault at src/gallium/drivers/radeon/r600_texture.c:602 Severity: normal Classification: Unclassified OS: Linux (All) Reporter: jzinkweg(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: 10.2 Component: Drivers/Gallium/r600 Product: Mesa Created attachment 105468 --> https://bugs.freedesktop.org/attachment.cgi?id=105468&action=edit GDB backtrace XCOM: Enemy Unknown segfaults frequently during gameplay. I have not been able to reliably reproduce a secenario, but playing 10-20 minutes usually ends in a crash to desktop, so if extra data is needed it is not that difficult for me to provide... I've attached GDB backtraces (simple and full) which suggest the crash is located in src/gallium/drivers/radeon/r600_texture.c. Running Debian Jessie 64 bit, with libgl1-mesa-dri 10.2.5 on an 512 MB ATI Mobility RADEON HD 4570 graphics card. -- You are receiving this mail because: You are the assignee for the bug.

1 9

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel September 2019