dri-devel June 2015

dri-devel@lists.freedesktop.org

188 participants
1140 discussions

[Bug 32325] New: [radeon] DRM version check only looks at minor number.
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=32325 Summary: [radeon] DRM version check only looks at minor number. Product: Mesa Version: git Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: rankincj(a)googlemail.com Created an attachment (id=41020) View: https://bugs.freedesktop.org/attachment.cgi?id=41020 Review: https://bugs.freedesktop.org/review?bug=32325&attachment=41020 [PATCH] Enable HyperZ and microtiling for R100 if DRM >= v2.x I have noticed that Mesa 7.9 prints the following message with a recent 2.6.3x kernel: "DRM version 1.6 too old to support HyperZ, disabling." The reason for this is that the DRM in the 2.6.36 kernel is v2.6: [drm] Initialized radeon 2.6.0 20080528 for 0000:01:00.0 on minor 0 and Mesa only checks the minor version number. (Assuming that the major version number is always 1.) I have attached a patch that will also enable both HyperZ and texture microtiling(?) on R100 if DRM >= v2.x. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 3

[Bug 30924] New: incorrect checking of return value of driAllocateTexture
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=30924 Summary: incorrect checking of return value of driAllocateTexture Product: Mesa Version: 7.8 Platform: All OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: ssb(a)umn.edu driAllocateTexture returns -1 for failure to allocate the texture. The code checks against NULL. [driAllocateTexture:631] unable to allocate texture Backtrace: 0: /usr/bin/X (xorg_backtrace+0x3b) [0x80ef15b] 1: /usr/bin/X (0x8048000+0x5cff5) [0x80a4ff5] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0xffffe410] 3: /usr/lib/dri/radeon_dri.so (0xb433a000+0x381bf) [0xb43721bf] 4: /usr/lib/libdrm_radeon.so.1 (radeon_cs_emit+0x14) [0xb70973d4] 5: /usr/lib/dri/radeon_dri.so (0xb433a000+0x35c78) [0xb436fc78] 6: /usr/lib/dri/radeon_dri.so (0xb433a000+0x35d2c) [0xb436fd2c] 7: /usr/lib/dri/radeon_dri.so (0xb433a000+0x35f32) [0xb436ff32] 8: /usr/lib/dri/radeon_dri.so (0xb433a000+0x17e0a) [0xb4351e0a] 9: /usr/lib/dri/radeon_dri.so (0xb433a000+0x75ccb) [0xb43afccb] 10: /usr/lib/dri/radeon_dri.so (0xb433a000+0x17b3c8) [0xb44b53c8] 11: /usr/lib/xorg/modules/extensions/libglx.so (0xb71b7000+0x83a0) [0xb71bf3a0] 12: /usr/lib/xorg/modules/extensions/libglx.so (0xb71b7000+0x31c45) [0xb71e8c45] 13: /usr/lib/xorg/modules/extensions/libglx.so (0xb71b7000+0x3645e) [0xb71ed45e] 14: /usr/bin/X (0x8048000+0x23707) [0x806b707] 15: /usr/bin/X (0x8048000+0x1dbb5) [0x8065bb5] 16: /lib/libc.so.6 (__libc_start_main+0xe6) [0xb7333a66] 17: /usr/bin/X (0x8048000+0x1d781) [0x8065781] Segmentation fault at address 0x14 -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 2

[Bug 84627] New: (bisected) 32bit corruption with PIPE_USAGE_STREAM reverted
by bugzilla-daemon＠freedesktop.org 22 Jul '19

22 Jul '19

https://bugs.freedesktop.org/show_bug.cgi?id=84627 Bug ID: 84627 Summary: (bisected) 32bit corruption with PIPE_USAGE_STREAM reverted Product: Mesa Version: git Hardware: x86 (IA32) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: smoki00790(a)gmail.com As Michel asks me here https://bugs.freedesktop.org/show_bug.cgi?id=82050#add_comment > (In reply to comment #65) > Keep in mind that revert broke 32bit complitely, lot of corruption :) >I haven't been able to reproduce that. If you still can, please file a bug for >it, as there's nothing preventing the kernel from using GTT instead of VRAM when >the latter is full. So i can reproduce it today too on 32bit (64bit is not affected, at least not by corruption) drm-next-3.18 kernel, 3.17.rc7, current mesa git and reverted this: http://lists.freedesktop.org/archives/mesa-dev/2014-August/066746.html For the mesa part, i already bisected that it starts at (might be same reason as bug 83436, but let alone that one for now): http://cgit.freedesktop.org/mesa/mesa/commit/?id=07c65b85eada8dd34019763b6e… For the kernel part not bisected yet, but it is somewhere in between 3.16 and 3.17-rc1, so hopefully i will bisect that maybe today :) -- You are receiving this mail because: You are the assignee for the bug.

1 43

[Bug 79417] New: r600-cayman: GPU lockup in Planetary Annihilation (PTE 66705) on HD6950
by bugzilla-daemon＠freedesktop.org 04 Jul '19

04 Jul '19

https://bugs.freedesktop.org/show_bug.cgi?id=79417 Priority: medium Bug ID: 79417 Assignee: dri-devel(a)lists.freedesktop.org Summary: r600-cayman: GPU lockup in Planetary Annihilation (PTE 66705) on HD6950 Severity: normal Classification: Unclassified OS: Linux (All) Reporter: sxx.public(a)yahoo.com Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/Gallium/r600 Product: Mesa Created attachment 100117 --> https://bugs.freedesktop.org/attachment.cgi?id=100117&action=edit dmesg output when GPU locked up This report partially related to bug 68527, but It's have to be new task because since yesterday's update game is using OpenGL 3.3 core profile which make it compatible with open source drivers. Game is tested and working on Intel HD4600 and LLVMPipe. Unfrortunately running it on HD6950 with R600 still result in GPU lockup. As in old task one of problems is complicated sun shader, but even if I remove this one I still get GPU lockup and I have no idea what else might cause issue. I made two traces using git version of APItrace, both traces takes when game running on Intel HD4600. First trace is with sun shader: https://drive.google.com/file/d/0B5LwC3WbdQ3DWjFJaVRiNndVdk0/edit?usp=shari… Second without sun shader: https://drive.google.com/file/d/0B5LwC3WbdQ3DOC1JVFhFTHdObVE/edit?usp=shari… Both traces lockup GPU and X when I try to replay them on HD6950. Useful part of "dmesg" output attached to task too. PS: My system info: Ubuntu 14.04 with kernel 3.14 and Mesa from Oibaf PPA: OpenGL Renderer: Gallium 0.4 on AMD CAYMAN OpenGL Version: 3.3 (Core Profile) Mesa 10.3.0-devel (git-ecee4c4 trusty-oibaf-ppa) -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 68527] New: Planetary Annihilation Alpha: translation from TGSI failed !
by bugzilla-daemon＠freedesktop.org 04 Jul '19

04 Jul '19

https://bugs.freedesktop.org/show_bug.cgi?id=68527 Priority: medium Bug ID: 68527 Assignee: dri-devel(a)lists.freedesktop.org Summary: Planetary Annihilation Alpha: translation from TGSI failed ! Severity: normal Classification: Unclassified OS: Linux (All) Reporter: sxx.public(a)yahoo.com Hardware: x86-64 (AMD64) Status: NEW Version: 9.2 Component: Drivers/Gallium/r600 Product: Mesa I test this game on my AMD HD6950 and Intel HD3000 both using latest Mesa 9.2. Problem with sun shader only occur with R600g. I can also notice that sun shader inside game based on this demo (which is working fine with R600): https://github.com/ashima/webgl-noise OpenGL vendor string: X.Org OpenGL renderer string: Gallium 0.4 on AMD CAYMAN OpenGL core profile version string: 3.1 (Core Profile) Mesa 9.2.0-devel OpenGL core profile shading language version string: 1.40 -- You are receiving this mail because: You are the assignee for the bug.

1 26

[Bug 37471] New: Website with information about maintainers/developers
by bugzilla-daemon＠freedesktop.org 29 May '19

29 May '19

https://bugs.freedesktop.org/show_bug.cgi?id=37471 Summary: Website with information about maintainers/developers Product: DRI Version: unspecified Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: medium Component: General AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: johannesobermayr(a)gmx.de There should be a website with information about main developers/maintainers: Product (DRM Intel, DRM Radeon, Mesa) | Component[s] (Maintainer, Core developer, Intel, R200, R300, R600, nouveau, ...) | Real Name | eMail | Name on IRC | Usual time to ask (e.g. 17 to 20 UTC) | Available on IRC channels (#dri-devel, #nouveau, ...) | Working for [Red Hat, SUSE, Linux Foundation, Ubuntu, ...] -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 2

[Bug 86351] New: HDMI audio garbled output on Radeon R9 280X
by bugzilla-daemon＠bugzilla.kernel.org 23 Mar '19

23 Mar '19

https://bugzilla.kernel.org/show_bug.cgi?id=86351 Bug ID: 86351 Summary: HDMI audio garbled output on Radeon R9 280X Product: Drivers Version: 2.5 Kernel Version: 3.17 Hardware: All OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: joker(a)netswarm.net Regression: No Created attachment 153891 --> https://bugzilla.kernel.org/attachment.cgi?id=153891&action=edit dmesg output Any sound played back over HDMI results in garbled audio output. When playing audio at 24000hz or below (19200Hz also tested) playback starts to work normaly without the constant choppyness. What also works is 44100Hz in Mono. It behaves like a data bandwith issue that kicks in above 24000hz Stereo or 44100Hz Mono. All test are done directly talking to the alsa device. This means no pulseaudio or dmix or similar processing. "plughw" had to be used because the hardware does not allow low rates like 24000. During all Test a perfectly fine and stable 1080p image is displayed over HDMI. (No dropouts at all). This hardware setup has also be successfully tested using Windows. (Incl. Multi channel PCM 6.0 for lot's of audio bandwidth) Working Audio Tests: -------------------- speaker-test -r 24000 -c2 speaker-test -r 24000 -c6 (multi channel PCM works too) mpg123 -r 24000 <file> mpg123 -m -r 44100 <file> The peer format detection is pcm 2.0 44100 or 48000 here. It appears the format link doesn't matter, only the actual data bandwidth that's being used) Garbled Audio Tests: -------------------- speaker-test -r 48000 -c2 speaker-test -r 48000 -c6 mpg123 -r 44100 <file> All passthru formats (dts, dolby d, pcm multi channel) get detected my the destination, but after a short period it loses the link and tries to resync. What previously also worked is a HD5570 in the same system which i no longer have access to though. Not sure about the kernel used back then. -- You are receiving this mail because: You are watching the assignee of the bug.

1 35

[Bug 88501] New: AMD/ATI RS690M Console blanks to white
by bugzilla-daemon＠bugzilla.kernel.org 05 Mar '19

05 Mar '19

https://bugzilla.kernel.org/show_bug.cgi?id=88501 Bug ID: 88501 Summary: AMD/ATI RS690M Console blanks to white Product: Drivers Version: 2.5 Kernel Version: 3.6.0-rc5 to 3.18.0-rc4 Hardware: x86-64 OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: business.kid(a)gmail.com Regression: Yes Created attachment 158181 --> https://bugzilla.kernel.org/attachment.cgi?id=158181&action=edit Git Bisect log, & git visualise o/p Without X running, linux consoles blank after a period adjustable by setterm. Mine does not. It goes white. If I invert the screen colours, it goes whiter. Backlight? I cloned the Linus-stable git and tried it. 3.18.0-rc4 twists this slightly - The FIRST time the screen blanks, it does so correctly; every other time, it blanks to white. I'm a hardware guy, not a software expert. Git bisect gives the output below. Details of the box also attached The box is a HP 6715S, twin core Turion, 3G ram. It's running Slackware-current as of Sept 30th, 2014. LSPCI output attached. Bios Version: ATI 02/13/08,1. -- You are receiving this mail because: You are watching the assignee of the bug.

1 11

[Bug 60623] New: White Screen on boot with radeon.dpm=1
by bugzilla-daemon＠bugzilla.kernel.org 05 Mar '19

05 Mar '19

https://bugzilla.kernel.org/show_bug.cgi?id=60623 Bug ID: 60623 Summary: White Screen on boot with radeon.dpm=1 Product: Drivers Version: 2.5 Kernel Version: 3.11.0-999-generic Hardware: x86-64 OS: Linux Tree: Mainline Status: NEW Severity: blocking Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: electrobs(a)gmail.com Regression: No Using the latest ubuntu built kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/, and enabling the boot option of radeon.dpm=1 . Results in a black screen after grub that eventually turns white gradually. Removing the option allows the laptop to function perfectly with the AMD 3650 video card. Hardware: -Lenovo T500 with AMD 3650 and a Intel 4500MHD switchable graphics off. -more info at http://support.lenovo.com/en_US/detail.page?LegacyDocID=MIGR-71785 Software: -clean install of Kubuntu 13.04 with beta ppa enabled for KDE 4.11 rc2 -xorg-edgers ppa enabled -- You are receiving this mail because: You are watching the assignee of the bug.

1 2

[Bug 91110] Textures missing iff character in specific areas in dolphin running Xenoblades Chronicles
by bugzilla-daemon＠freedesktop.org 17 Feb '19

17 Feb '19

https://bugs.freedesktop.org/show_bug.cgi?id=91110 Bug ID: 91110 Summary: Textures missing iff character in specific areas in dolphin running Xenoblades Chronicles Product: Mesa Version: git Hardware: x86-64 (AMD64) URL: https://code.google.com/p/dolphin-emu/issues/detail?id =8688 OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: christian(a)madez.de QA Contact: dri-devel(a)lists.freedesktop.org Iff a character is in specific areas some textures on him are not rendered. In the entry of colony 9 is such an area. The textures are rendered properly on the Intel GPU. There are screenshots, a fifolog and an apitrace at the end of the linked bugreport. The problem appears in Debian Jessie, Sid and mesa-git the last time checked, which was 9 days ago. I compiled mesa-git with CFLAGS = -g -O2 -Wall -std=c99 -Werror=implicit-function-declaration -Werror=missing-prototypes -fno-strict-aliasing -fno-builtin-memcmp -DDEBUG and set $ export LIBGL_DEBUG=verbose $ export MESA_DEBUG=1 $ export EGL_LOG_LEVEL=debug before running dolphin. Running dolphin with the game until the issue appears gives the following output $ dolphin-emu Gtk-Message: Failed to load module "canberra-gtk-module" libGL: screen 0 does not appear to be DRI3 capable libGL: pci id for fd 22: 1002:679a, driver radeonsi libGL: OpenDriver: trying lib/tls/radeonsi_dri.so libGL: OpenDriver: trying lib/radeonsi_dri.so libGL: Can't open configuration file /home/user/.drirc: Arquivo ou diretório não encontrado. libGL: Can't open configuration file /home/user/.drirc: Arquivo ou diretório não encontrado. libGL: Using DRI2 for screen 0 I'm sorry, I don't know how to write a simple GLUT-based test program. -- You are receiving this mail because: You are the assignee for the bug.

1 7

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel June 2015