dri-devel March 2015

dri-devel@lists.freedesktop.org

196 participants
1117 discussions

[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 85791] New: nouveau: errors on boot, can't use discrete gpu
by bugzilla-daemon＠bugzilla.kernel.org 03 Dec '18

03 Dec '18

https://bugzilla.kernel.org/show_bug.cgi?id=85791 Bug ID: 85791 Summary: nouveau: errors on boot, can't use discrete gpu Product: Drivers Version: 2.5 Kernel Version: 3.16.4, 3.14.20 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: mezin.alexander(a)gmail.com Regression: No Created attachment 152791 --> https://bugzilla.kernel.org/attachment.cgi?id=152791&action=edit dmesg On boot I see these errors: [ 18.929898] nouveau E[ PBUS][0000:01:00.0] MMIO write of 0x00000002 FAULT at 0x4188ac [ IBUS ] [ 18.931250] nouveau E[ DRM] Pointer to TMDS table invalid [ 18.932395] nouveau E[ DRM] Pointer to flat panel table invalid [ 22.798349] nouveau E[ PGRAPH][0000:01:00.0] HUB_INIT timed out [ 22.798360] nouveau E[ PGRAPH][0000:01:00.0] 409000 - done 0x00000220 [ 22.798373] nouveau E[ PGRAPH][0000:01:00.0] 409000 - stat 0x00000000 0x00000000 0x00000000 0x00000000 [ 22.798384] nouveau E[ PGRAPH][0000:01:00.0] 409000 - stat 0x00000000 0x00000000 0x00000006 0x00000001 [ 22.798389] nouveau E[ PGRAPH][0000:01:00.0] 502000 - done 0x00000300 [ 22.798397] nouveau E[ PGRAPH][0000:01:00.0] 502000 - stat 0x00000000 0x00008c00 0x00000000 0x00000000 [ 22.798404] nouveau E[ PGRAPH][0000:01:00.0] 502000 - stat 0x00000000 0x00000000 0x00000000 0x00000000 [ 22.798406] nouveau E[ PGRAPH][0000:01:00.0] init failed, -16 Full dmesg is attached. When I try to use discrete gpu with DRI_PRIME=1 (after xrandr --setprovideroffloadsink), X crashes. Hardware: 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 09) 01:00.0 3D controller: NVIDIA Corporation GK107M [GeForce GT 750M] (rev a1) Acer Aspire V5-573G If I remember correctly, some time ago everything worked. -- You are receiving this mail because: You are watching the assignee of the bug.

1 7

[Bug 82717] New: OpenCL support for mandelbulber-opencl
by bugzilla-daemon＠freedesktop.org 09 Sep '18

09 Sep '18

https://bugs.freedesktop.org/show_bug.cgi?id=82717 Priority: medium Bug ID: 82717 Assignee: dri-devel(a)lists.freedesktop.org Summary: OpenCL support for mandelbulber-opencl Severity: normal Classification: Unclassified OS: All Reporter: haagch(a)frickel.club Hardware: Other Status: NEW Version: git Component: Drivers/Gallium/radeonsi Product: Mesa Website of the program here: https://sites.google.com/site/mandelbulber/ (Watch out, it uses a weird install script) Start it, go to the OpenCL tab and try to enable OpenCL. A few things that probably need to be addressed. I applied some workarounds to see them all and I don't even know if the OpenCL programs would work after removing all of that stuff. Problem 1: OpenCL Build log: ERROR: Program::build() (-43) That's because of the build paramater -cl-denorms-are-zero that is hardcoded in the source code of mandelbulber. Workarodund 1: sed -i 's/-cl-denorms-are-zero / /g' src/cl_support.cpp Problem 2: OpenCL Build log: input.cl:34:1: error: OpenCL does not support the 'static' storage class specifier So that's not valid in OpenCL 1.1, but for the sake of getting it to "just compile" at least: Workaround 2: for i in /usr/share/mandelbulber/cl/*; do sed -i "s/static //g" $i; done Problem 3: OpenCL Build log: input.cl:323:10: error: cannot combine with previous 'type-name' declaration specifier input.cl:323:15: error: expected identifier or '(' input.cl:324:8: error: expected identifier or '(' input.cl:325:32: error: expected expression � (WTF is random binary data doing here?) That's a weird one that seems to come from whatever clang does. I think clang thinks that "half" is already defined in the OpenCL kernels. Not sure if this is intended. Workaround 3: for i in /usr/share/mandelbulber/cl/*; do sed -i "s/half /halfFOO /g" $i; done for i in /usr/share/mandelbulber/cl/*; do sed -i "s/half)/halfFOO)/g" $i; done Problem 4: OpenCL Build log: �}� OpenCL program built done OpenCL kernel opened OpenCL workgroup size: 256 OpenCL Job size: 480256 terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc I don't think the crash itself is the fault of mesa opencl, because the backtrace looks like this: #0 0x00007fd1154e2d67 in raise () from /usr/lib/libc.so.6 #1 0x00007fd1154e4118 in abort () from /usr/lib/libc.so.6 #2 0x00007fd115dd81f5 in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/libstdc++.so.6 #3 0x00007fd115dd6076 in ?? () from /usr/lib/libstdc++.so.6 #4 0x00007fd115dd60c1 in std::terminate() () from /usr/lib/libstdc++.so.6 #5 0x00007fd115dd62d8 in __cxa_throw () from /usr/lib/libstdc++.so.6 #6 0x00007fd115dd6869 in operator new(unsigned long) () from /usr/lib/libstdc++.so.6 #7 0x00007fd115dd68c9 in operator new[](unsigned long) () from /usr/lib/libstdc++.so.6 #8 0x00000000004a3683 in CclSupport::InitFractal (this=0x207e200) at ../src/cl_support.cpp:451 #9 0x000000000042cffb in ChangedOpenClEnabled (widget=0x22bdd60, data=0x0) at ../src/callbacks.cpp:2896 #10 0x00007fd11673b3d8 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0 #11 0x00007fd11674cd5d in ?? () from /usr/lib/libgobject-2.0.so.0 But why is there random binary data in the OpenCL build log? llvm-svn 215809 libclc-git 165.20140816 opencl-headers12 1:1.2.r26859 (not sure if relevant) mesa git from today radeon 7970M pitcairn -- You are receiving this mail because: You are the assignee for the bug.

1 12

[Bug 87738] Please add Image support
by bugzilla-daemon＠freedesktop.org 09 Sep '18

09 Sep '18

https://bugs.freedesktop.org/show_bug.cgi?id=87738 Bug ID: 87738 Summary: Please add Image support Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: enhancement Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: mercen45(a)gmail.com Hi, Image support is required by darktable (RAW photos processing) as can be seen in the following output, from runnind darktable -d opencl: [opencl_init] opencl related configuration options: [opencl_init] [opencl_init] opencl: 0 [opencl_init] opencl_library: '' [opencl_init] opencl_memory_requirement: 768 [opencl_init] opencl_memory_headroom: 300 [opencl_init] opencl_device_priority: '*/!0,*/*/*' [opencl_init] opencl_size_roundup: 16 [opencl_init] opencl_async_pixelpipe: 0 [opencl_init] opencl_synch_cache: 0 [opencl_init] opencl_number_event_handles: 25 [opencl_init] opencl_micro_nap: 1000 [opencl_init] opencl_use_pinned_memory: 0 [opencl_init] opencl_use_cpu_devices: 0 [opencl_init] opencl_avoid_atomics: 0 [opencl_init] opencl_omit_whitebalance: 0 [opencl_init] [opencl_init] trying to load opencl library: '<system default>' [opencl_init] opencl library 'libOpenCL' found on your system and loaded [opencl_init] found 1 platform [opencl_init] found 1 device [opencl_init] discarding device 0 `AMD OLAND' due to missing image support. [opencl_init] no suitable devices found. [opencl_init] FINALLY: opencl is NOT AVAILABLE on this system. [opencl_init] initial status of opencl enabled flag is OFF. Not sure if anything else is needed to get OpenCL to work in darktable but it would be very sweet to be able to get that with open source drivers. Thanks, Thomas -- You are receiving this mail because: You are the assignee for the bug.

1 10

[Bug 68085] New: Xorg crash in do_winsys_init
by bugzilla-daemon＠freedesktop.org 31 Aug '18

31 Aug '18

https://bugs.freedesktop.org/show_bug.cgi?id=68085 Priority: medium Bug ID: 68085 Assignee: dri-devel(a)lists.freedesktop.org Summary: Xorg crash in do_winsys_init Severity: normal Classification: Unclassified OS: All Reporter: luto(a)mit.edu Hardware: Other Status: NEW Version: git Component: Drivers/DRI/Radeon Product: Mesa Created attachment 84033 --> https://bugs.freedesktop.org/attachment.cgi?id=84033&action=edit Relevant bits of dmesg My box has mgag200 primary and radeon (HD7750) secondary. Xorg crashes on startup in do_winsys_init, which is passed fd = -1. The crash is because drmGetVersion returns NULL. 'rmmod radeon' allows X to start (but without the radeon device). This is Fedora 19, fully up to date. The install disk has the same problem. I'm not sure where fd is supposed to be set to something real, so this bug might be targeting the wrong thing. (gdb) bt full [10/139] #0 do_winsys_init (ws=0x2ff7f20) at radeon_drm_winsys.c:212 gem_info = {gart_size = 0, vram_size = 0, vram_visible = 0} retval = <optimized out> version = <optimized out> #1 radeon_drm_winsys_create (fd=-1) at radeon_drm_winsys.c:617 ws = 0x2ff7f20 #2 0x00007fc2dd8fd359 in create_screen (fd=<optimized out>) at target.c:11 radeon = <optimized out> screen = <optimized out> #3 0x00007fc2ddbc5c32 in dri2_init_screen (sPriv=0x2ff7e00) at dri2.c:888 configs = <optimized out> screen = 0x2ff7e90 pscreen = <optimized out> throttle_ret = 0x0 #4 0x00007fc2dae2e2dd in driCreateNewScreen (scrn=0, extensions=0x7fc2df941b50 <loader_extensions>, driver_configs=0x2f76700, data=0x2f76660) at ../../../../src/mesa/drivers/dri/common/drisw_util.c:70 emptyExtensionList = {0x0} psp = 0x2ff7e00 #5 0x00007fc2df713b91 in __glXDRIscreenProbe (pScreen=0x2f473b0) at glxdriswrast.c:458 driverName = 0x7fc2df72e2a6 "swrast" screen = 0x2f76660 #6 0x00007fc2df71315a in GlxExtensionInit () at glxext.c:355 glxScreen = <optimized out> extEntry = <optimized out> pScreen = 0x2f473b0 i = 0 p = 0x7fc2df941b20 <__glXDRISWRastProvider> stack = <optimized out> glx_provided = 0 #7 0x00000000004ba1a1 in InitExtensions (argc=argc@entry=1, argv=argv@entry=0x7fff9f7860a8) at ../../../mi/miinitext.c:337 i = <optimized out> ext = <optimized out> #8 0x00000000004262e0 in main (argc=1, argv=0x7fff9f7860a8, envp=<optimized out>) at main.c:208 i = <optimized out> alwaysCheckForInput = {0, 1} -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 88925] GPU lockup in XCOM with R270X
by bugzilla-daemon＠freedesktop.org 31 Aug '18

31 Aug '18

https://bugs.freedesktop.org/show_bug.cgi?id=88925 Bug ID: 88925 Summary: GPU lockup in XCOM with R270X Product: DRI Version: DRI git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: dex+fdobugzilla(a)dragonslave.de Created attachment 113074 --> https://bugs.freedesktop.org/attachment.cgi?id=113074&action=edit First stall I'm seeing a constant number of GPU lockups in this game. About 5-10 Minutes in Game right after anything happens on screen that looks like it may need some more GPU power it freezes. Hardware: 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Pitcairn (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. Device 3036 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 34 Region 0: Memory at c0000000 (64-bit, prefetchable) [size=256M] Region 2: Memory at fea00000 (64-bit, non-prefetchable) [size=256K] Region 4: I/O ports at e000 [size=256] Expansion ROM at fea40000 [disabled] [size=128K] Capabilities: [48] Vendor Specific Information: Len=08 <?> Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1+,D2+,D3hot+,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [58] Express (v2) Legacy Endpoint, MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s <4us, L1 unlimited ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset- DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+ MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr- TransPend- LnkCap: Port #0, Speed 8GT/s, Width x16, ASPM L0s L1, Latency L0 <64ns, L1 <1us ClockPM- Surprise- LLActRep- BwNot- LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 5GT/s, Width x16, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete-, EqualizationPhase1- EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest- Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Address: 00000000fee00000 Data: 0000 Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [150 v2] Advanced Error Reporting UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol- CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn- Capabilities: [270 v1] #19 Capabilities: [2b0 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable+, Smallest Translation Unit: 00 Capabilities: [2c0 v1] #13 Capabilities: [2d0 v1] #1b Kernel driver in use: radeon Software: * Kernel 3.19.0-rc7-13532-g1b7a4a0 * xorg-server 1.16.3 * llvm SVN 227800 * Mesa 10.5.0-devel (git-af8fd69) * xf86-video-ati 7.5.0 -- You are receiving this mail because: You are the assignee for the bug.

1 8

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel March 2015