dri-devel September 2019

dri-devel@lists.freedesktop.org

315 participants
2278 discussions

[Bug 30651] New: r600g: gl output in mplayer have no colors if used with a fragment program with additional lookup and bicubic B-spline filtering
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=30651 Summary: r600g: gl output in mplayer have no colors if used with a fragment program with additional lookup and bicubic B-spline filtering Product: Mesa Version: git Platform: All OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: virtuousfox(a)gmail.com when i try to play video in mplayer with option 'gl:yuv=4,lscale=1,cscale=1' and r600g in use, it displays no colors. if it's 'gl:yuv=3', colors are ok. 'gl:yuv=5' seems also ok. sorry, i haven't tested yuv=4 without 'lscale=1,cscale=1' and immediately rebuilded mesa without gallium, so i don't know which of those to blame actually. my bet is 'yuv=4' and "a fragment program with additional lookup". by the way, what yuv and *scale options do you recommend for use with ATI/AMD >=r600 cards in terms of performance and quality ? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 10

[Bug 25280] r600: glPolygonStipple broken
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=25280 GitLab Migration User <gitlab-migration(a)fdo.invalid> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |MOVED --- Comment #9 from GitLab Migration User <gitlab-migration(a)fdo.invalid> --- -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/390. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 110914] Heavy corruption on R300 with modesetting and GLAMOR
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=110914 Bug ID: 110914 Summary: Heavy corruption on R300 with modesetting and GLAMOR Product: Mesa Version: git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r300 Assignee: dri-devel(a)lists.freedesktop.org Reporter: rsalvaterra(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 144533 --> https://bugs.freedesktop.org/attachment.cgi?id=144533&action=edit Corrupted login screen (lightdm on Ubuntu MATE 19.04) There's heavy corruption when using modesetting and GLAMOR on R300 (Radeon Xpress 200M). R500 (Mobility Radeon X1600) works fine. Attached is a photo displaying the problem. -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 110897] HyperZ is broken for r300 (bad z for some micro and macrotiles?)
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=110897 Bug ID: 110897 Summary: HyperZ is broken for r300 (bad z for some micro and macrotiles?) Product: Mesa Version: git Hardware: Other OS: other Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r300 Assignee: dri-devel(a)lists.freedesktop.org Reporter: u9vata(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 144505 --> https://bugs.freedesktop.org/attachment.cgi?id=144505&action=edit first screenshot (still not completely ruined zbuffer) Hello everyone! I went on and tried RADEON_HYPERZ=1 with my r300 card and I see bad glitches - while in the same time elevated performance. See attached screenshot(s). This affect every application, even the simplest ones like glxgears. The top of the screen is rendering properly always, but around the 25% of the screen it starts to break down and I can see tiles where things seem to have a really bad z-value. What is also interesting is that [b]I feel the z-clear is the operation that is happening wrong[/b]! I am pretty sure in this because at the first few frames of glxgears I can nearly see all the gears and as the gears turn, I see less and less of them - it kind of feels that whenever some pixel got rendered, its place cannot be used anymore - or likely cannot be used! If I turn the wheels some times around the Y axis the bottom 2/3 of the screen just becomes completely dark after a while. If I exit glxgears - or any app in question of testing - and restart it from the terminal however, I see that everything is immediately wrong! So [b]the problem persists between multiple runs of the same program with same sized window[/b] and this also hints that the z buffer is never properly (or at all) cleared! BUT [b]resizing the window immediately fixes the current frame[/b] with seemingly proper Z-values and if I keep resizing I can see a constant flickering - but a much more clear image. I think the resize operation triggers some resize in the buffers that cleans them properly, but in the very first second it already gets wrong again pretty much and this is what is happening. Also while resizing the window I saw that [b]there is no straight horizontal cut above which things are good and below which things are bad, but I literally see only the number of (macro?)tiles count from the top-left corner![/b] So basically I can see the side of one of the macrotiles. I tried to picture this with a screenshot, but it is not that easy to resize that way. See the second sceenshot that does not have anything on the bottom, but you see the cut and the left side of the tile where first things got wrong. Also the order of how the tiles go wrong is not always linear, but the first ones always work - from top-left going just like pixels. I am trying to use documentation that I have found here: http://renderingpipeline.com/graphics-literature/low-level-gpu-documentatio… Of course the r300 register docs should be good I hope, but I started reading through the r500_acceleration docs as it seems many-many of it applies to all r300 cards. Am I right that these are the best sources so far? To be honest I think the fast z-clear maybe is the problem and is badly configured to only clear the top few tiles on the screen or something similar. The tiles are approximately 32x32 or 16x16, but surely not just 1-2 pixels as they are pretty much visible to the naked eye (see second attachment screenshot). I have just barely started my analysis, so I still have a lot of directions to take and the docs (if they are good) are really helpful at least! I did not know about them so far!!! Currently playing around the code to see if I can help the problem disappear. This is likely never worked. I do not know of any version where this worked on my machine, but I cannot completely rule it out of course. -- You are receiving this mail because: You are the assignee for the bug.

1 75

[Bug 108576] Radeon driver crashes all PCI devices on the system
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=108576 Bug ID: 108576 Summary: Radeon driver crashes all PCI devices on the system Product: Mesa Version: 18.0 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: Drivers/Gallium/r300 Assignee: dri-devel(a)lists.freedesktop.org Reporter: brais.1997(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 142230 --> https://bugs.freedesktop.org/attachment.cgi?id=142230&action=edit dmesg after triggering the bug. I have a problem with an old HP Compaq NW8440 computer running Linux. The computer runs really fine except for some bugs. This is the most critical one, if I run a software that uses 3D acceleration, sometimes the entire system crashes and I have to reset the computer manually. -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 106289] mupen64plus segfaults deep inside r300_dri.so
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=106289 Bug ID: 106289 Summary: mupen64plus segfaults deep inside r300_dri.so Product: DRI Version: XOrg git Hardware: x86 (IA32) OS: Linux (All) Status: NEW Severity: blocker Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: dcoffin(a)cybercom.net Dell Vostro 1000 laptop with Mobile AMD Sempron, Mobility Radeon Xpress 200, and 32-bit Linux (though CPU is capable of 64-bit). "apt install mupen64plus", run it with any game ROM -- it opens an all-black window, pauses for a few seconds, and segfaults in r300_dri.so. mupen64plus worked great in Kubuntu 17.04 but always crashes in 17.10 and 18.04. Video: SSE processing enabled. Video: Found ROM 'SUPER MARIO 64', CRC ff2b5a632623028b-45 Video: Initializing OpenGL Device Context. warning: Error reading shared library list entry at 0x5f20 warning: Error reading shared library list entry at 0xffffbf40 Core: Setting 32-bit video mode: 640x480 Video Warning: Failed to set GL_SWAP_CONTROL to 0. (it's 24) Video Warning: Failed to set GL_BUFFER_SIZE to 32. (it's 24) Video Warning: Failed to set GL_DEPTH_SIZE to 16. (it's 24) Video: Using OpenGL: X.Org R300 Project - ATI RS480 : 2.1 Mesa 18.0.0-rc5 Thread 1 "mupen64plus" received signal SIGSEGV, Segmentation fault. 0xb4a83200 in ?? () (gdb) where #0 0xb4a83200 in ?? () #1 0xb33fff48 in ?? () from /usr/lib/i386-linux-gnu/dri/r300_dri.so #2 0xb34004df in ?? () from /usr/lib/i386-linux-gnu/dri/r300_dri.so #3 0xb33132f9 in ?? () from /usr/lib/i386-linux-gnu/dri/r300_dri.so #4 0xb330c1c0 in ?? () from /usr/lib/i386-linux-gnu/dri/r300_dri.so #5 0xb330c6b7 in ?? () from /usr/lib/i386-linux-gnu/dri/r300_dri.so #6 0xb353e21b in ?? () from /usr/lib/i386-linux-gnu/dri/r300_dri.so #7 0xb33511e4 in ?? () from /usr/lib/i386-linux-gnu/dri/r300_dri.so #8 0xb353fcd5 in ?? () from /usr/lib/i386-linux-gnu/dri/r300_dri.so #9 0xb33539ee in ?? () from /usr/lib/i386-linux-gnu/dri/r300_dri.so #10 0xb35342b6 in ?? () from /usr/lib/i386-linux-gnu/dri/r300_dri.so #11 0xb3127955 in ?? () from /usr/lib/i386-linux-gnu/dri/r300_dri.so #12 0xb2f7892f in ?? () from /usr/lib/i386-linux-gnu/dri/r300_dri.so #13 0xb4caa82d in ?? () from /usr/lib/i386-linux-gnu/mupen64plus/mupen64plus-video-rice.so -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 105273] [r350] missing background, transparency not working & other glitches in ETR (AGP, ppc, mesa-18.0.0_rc4)
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=105273 Bug ID: 105273 Summary: [r350] missing background, transparency not working & other glitches in ETR (AGP, ppc, mesa-18.0.0_rc4) Product: Mesa Version: git Hardware: PowerPC OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r300 Assignee: dri-devel(a)lists.freedesktop.org Reporter: erhard_f(a)mailbox.org QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 137657 --> https://bugs.freedesktop.org/attachment.cgi?id=137657&action=edit ETR on ppc, pic 0 I know, I know - yet another bug of something not working on ppc. But actually things have improved in the meantime. Since a complete system & kernel rebuild with gcc 7.3.0 my AGP Radeon 9650 and 9800 started working decently (see bug #105254). And mesa 18.0.0_rc4 certainly shows less glitches than 17.2.x and the versions before. Colors are right and Extreme Tux Racer runs smoothly. What's not working is transparency and the background is missing too. Another thing is this strange misplacement of trees and the start/finish banner on the track (lying on the side instead of standing). I'll add pictures, you will notice immediately what I mean. -- You are receiving this mail because: You are the assignee for the bug.

1 9

[Bug 105254] piglit tests/sanity.py fail on ppc, mesa-18.0.0_rc4
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=105254 Bug ID: 105254 Summary: piglit tests/sanity.py fail on ppc, mesa-18.0.0_rc4 Product: Mesa Version: git Hardware: PowerPC OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r300 Assignee: dri-devel(a)lists.freedesktop.org Reporter: erhard_f(a)mailbox.org QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 137606 --> https://bugs.freedesktop.org/attachment.cgi?id=137606&action=edit results/sanity/results.json.bz2 Building piglit went fine, but the sanity tests fail. OpenGL software, e.g. extreme tuxracer runs, but with some glitches. Machine is a PowerMac G5 7,3 + AGP Radeon 9800: # inxi -b System: Host: T800 Kernel: 4.15.5-gentoo ppc64 bits: 32 Desktop: MATE 1.18.0 Distro: Gentoo Base System release 2.4.1 Machine: No /sys/class/dmi; using dmidecode: dmidecode is not installed. CPU: Dual core PPC970FX altivec supported (-MCP-) speed/max: 2300.000000MHz/2300 MHz Graphics: Card: Advanced Micro Devices [AMD/ATI] R350 [Radeon 9800 Series] Display Server: x11 (X.Org 1.19.5 ) driver: radeon Resolution: 1920x1080(a)60.00hz OpenGL: renderer: ATI R350 version: 2.1 Mesa 18.0.0-rc4 Network: Card: Apple K2 GMAC (Sun GEM) driver: gem # glxinfo | grep -i opengl r300: DRM version: 2.50.0, Name: ATI R350, ID: 0x4e48, GB: 2, Z: 1 r300: GART size: 253 MB, VRAM size: 256 MB r300: AA compression RAM: YES, Z compression RAM: YES, HiZ RAM: YES OpenGL vendor string: X.Org R300 Project OpenGL renderer string: ATI R350 OpenGL version string: 2.1 Mesa 18.0.0-rc4 OpenGL shading language version string: 1.20 OpenGL extensions: r300: DRM version: 2.50.0, Name: ATI R350, ID: 0x4e48, GB: 2, Z: 1 r300: GART size: 253 MB, VRAM size: 256 MB r300: AA compression RAM: YES, Z compression RAM: YES, HiZ RAM: YES OpenGL ES profile version string: OpenGL ES 2.0 Mesa 18.0.0-rc4 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 1.0.16 OpenGL ES profile extensions: -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 103630] [regression] Hacker Evolution(1,2,3) crash on startup
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=103630 Bug ID: 103630 Summary: [regression] Hacker Evolution(1,2,3) crash on startup Product: Mesa Version: 17.2 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r300 Assignee: dri-devel(a)lists.freedesktop.org Reporter: cosiekvfj(a)o2.pl QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 135319 --> https://bugs.freedesktop.org/attachment.cgi?id=135319&action=edit Hacker Evolution trace -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 101382] [r300] Electronic super joy crash on 17.1.0 (17.0.5 is ok)
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=101382 Bug ID: 101382 Summary: [r300] Electronic super joy crash on 17.1.0 (17.0.5 is ok) Product: Mesa Version: 17.1 Hardware: x86-64 (AMD64) OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r300 Assignee: dri-devel(a)lists.freedesktop.org Reporter: cosiekvfj(a)o2.pl QA Contact: dri-devel(a)lists.freedesktop.org Ok. Something is really weird. This game is crashing on 17.1.0. I'm confused because of https://bugs.freedesktop.org/show_bug.cgi?id=98869. Game is rendering properly on 17.0.5. It looks like this patch wasn't a real solution and now it is causing this bug. Then I didn't checked when this patch was merged and assumed it was and that's why game was working. Or this is true or the world appears not to be rational… -- You are receiving this mail because: You are the assignee for the bug.

1 18

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel September 2019