dri-devel September 2014

dri-devel@lists.freedesktop.org

173 participants
1045 discussions

[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 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 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 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 82455] New: Failed to allocate virtual address for buffer
by bugzilla-daemon＠freedesktop.org 31 Aug '18

31 Aug '18

https://bugs.freedesktop.org/show_bug.cgi?id=82455 Priority: medium Bug ID: 82455 Assignee: dri-devel(a)lists.freedesktop.org Summary: Failed to allocate virtual address for buffer Severity: normal Classification: Unclassified OS: Linux (All) Reporter: 407883775(a)qq.com Hardware: SPARC Status: NEW Version: 9.2 Component: Drivers/Gallium/radeonsi Product: Mesa I am update kernel to 3.10.0 , and the mesa version is 9.2.5; Our video card is AMD HD7750 . The system is running very well in text mode. But when I am used startx command start graphic desktop. The X can't work. Our team analysis the problem and read the mesa code. Due to Mesa , I think. our computer arch is "sparc" I sought you commit the bug in the freedesktoporg : http://cgit.freedesktop.org/mesa/mesa/commit/?id=a37835c8eda017f0c955e0927e… but the mesa (version 9.2.5) have this bug. how could i do . pls give me some message . thk . The attachment is system dmesg . The debug message is follow: [dmesg] [ 355.852288] radeon 0000:01:00.0: soffset:0x00100000, eoffset: 0x00200000 [ 355.853024] radeon 0000:01:00.0: tmp->soffset:0x00000000, tmp->eoffset: 0x00000000, size:0x00100000 [ 359.114368] radeon 0000:01:00.0: soffset:0x00100000, eoffset: 0x00200000 [ 359.114399] radeon 0000:01:00.0: tmp->soffset:0x00000000, tmp->eoffset: 0x00000000, size:0x00100000 [ 359.433678] radeon 0000:01:00.0: soffset:0x00100000, eoffset: 0x00200000 [ 359.433711] radeon 0000:01:00.0: tmp->soffset:0x00000000, tmp->eoffset: 0x00000000, size:0x00100000 [ 359.433891] radeon 0000:01:00.0: soffset:0x00100000, eoffset: 0x00200000 [ 359.433915] radeon 0000:01:00.0: tmp->soffset:0x00000000, tmp->eoffset: 0x00000000, size:0x00100000 [ 519.314418] radeon 0000:01:00.0: soffset:0x00100000, eoffset: 0x00200000 [ 519.314453] radeon 0000:01:00.0: tmp->soffset:0x00000000, tmp->eoffset: 0x00000000, size:0x00100000 [ 521.768715] radeon 0000:01:00.0: soffset:0x00100000, eoffset: 0x00200000 [ 521.768746] radeon 0000:01:00.0: tmp->soffset:0x00000000, tmp->eoffset: 0x00000000, size:0x00100000 [ 522.077890] radeon 0000:01:00.0: soffset:0x00100000, eoffset: 0x00200000 [ 522.077924] radeon 0000:01:00.0: tmp->soffset:0x00000000, tmp->eoffset: 0x00000000, size:0x00100000 [ 522.078105] radeon 0000:01:00.0: soffset:0x00100000, eoffset: 0x00200000 [ 522.078129] radeon 0000:01:00.0: tmp->soffset:0x00000000, tmp->eoffset: 0x00000000, size:0x00100000 [ 565.368145] radeon 0000:01:00.0: [radeon_gem_va_ioctl, 525]:args->offset: 0x00800000, argx->flags:22 [ 565.368180] radeon 0000:01:00.0: soffset:0x00800000, eoffset: 0x00802000 [ 565.368201] radeon 0000:01:00.0: tmp->soffset:0x00000000, tmp->eoffset: 0x00000000, size:0x00002000 [ 565.368221] radeon 0000:01:00.0: tmp->soffset:0x00100000, tmp->eoffset: 0x00200000, size:0x00002000 [ 763.251113] radeon 0000:01:00.0: [radeon_gem_va_ioctl, 525]:args->offset: 0x00801000, argx->flags:22 [ 763.251148] radeon 0000:01:00.0: soffset:0x00801000, eoffset: 0x00803000 [ 763.251169] radeon 0000:01:00.0: tmp->soffset:0x00000000, tmp->eoffset: 0x00000000, size:0x00002000 [ 763.251189] radeon 0000:01:00.0: tmp->soffset:0x00100000, tmp->eoffset: 0x00200000, size:0x00002000 [ 763.251210] radeon 0000:01:00.0: tmp->soffset:0x00800000, tmp->eoffset: 0x00802000, size:0x00002000 [ 763.251234] radeon 0000:01:00.0: bo fffff801f3ee2c00 va 0x00000000 conflict with (bo fffff801f3ee3000 0x00800000 0x00802000) [ 763.251855] radeon 0000:01:00.0: [radeon_gem_va_ioctl, 525]:args->offset: 0x00801000, argx->flags:22 [ 763.251878] radeon 0000:01:00.0: soffset:0x00801000, eoffset: 0x00803000 [ 763.251899] radeon 0000:01:00.0: tmp->soffset:0x00000000, tmp->eoffset: 0x00000000, size:0x00002000 [ 763.251919] radeon 0000:01:00.0: tmp->soffset:0x00100000, tmp->eoffset: 0x00200000, size:0x00002000 [ 763.251939] radeon 0000:01:00.0: tmp->soffset:0x00800000, tmp->eoffset: 0x00802000, size:0x00002000 [ 763.251962] radeon 0000:01:00.0: bo fffff801f3ee2c00 va 0x00000000 conflict with (bo fffff801f3ee3000 0x00800000 0x00802000) [ 884.626830] radeon 0000:01:00.0: soffset:0x00100000, eoffset: 0x00200000 [ 884.626864] radeon 0000:01:00.0: tmp->soffset:0x00000000, tmp->eoffset: 0x00000000, size:0x00100000 [ 887.207173] radeon 0000:01:00.0: soffset:0x00100000, eoffset: 0x00200000 [ 887.207204] radeon 0000:01:00.0: tmp->soffset:0x00000000, tmp->eoffset: 0x00000000, size:0x00100000 [ 887.564451] radeon 0000:01:00.0: soffset:0x00100000, eoffset: 0x00200000 [ 887.564488] radeon 0000:01:00.0: tmp->soffset:0x00000000, tmp->eoffset: 0x00000000, size:0x00100000 [ 887.564672] radeon 0000:01:00.0: soffset:0x00100000, eoffset: 0x00200000 [ 887.564696] radeon 0000:01:00.0: tmp->soffset:0x00000000, tmp->eoffset: 0x00000000, size:0x00100000 [ 985.395298] radeon 0000:01:00.0: soffset:0x00100000, eoffset: 0x00200000 [ 985.395332] radeon 0000:01:00.0: tmp->soffset:0x00000000, tmp->eoffset: 0x00000000, size:0x00100000 [ 987.861353] radeon 0000:01:00.0: soffset:0x00100000, eoffset: 0x00200000 [ 987.861387] radeon 0000:01:00.0: tmp->soffset:0x00000000, tmp->eoffset: 0x00000000, size:0x00100000 [ 988.175840] radeon 0000:01:00.0: soffset:0x00100000, eoffset: 0x00200000 [ 988.175873] radeon 0000:01:00.0: tmp->soffset:0x00000000, tmp->eoffset: 0x00000000, size:0x00100000 [ 988.176054] radeon 0000:01:00.0: soffset:0x00100000, eoffset: 0x00200000 [ 988.176078] radeon 0000:01:00.0: tmp->soffset:0x00000000, tmp->eoffset: 0x00000000, size:0x00100000 -- You are receiving this mail because: You are the assignee for the bug.

1 37

[Bug 80690] New: Suddenly X halts
by bugzilla-daemon＠freedesktop.org 31 Aug '18

31 Aug '18

https://bugs.freedesktop.org/show_bug.cgi?id=80690 Priority: medium Bug ID: 80690 Assignee: dri-devel(a)lists.freedesktop.org Summary: Suddenly X halts Severity: normal Classification: Unclassified OS: All Reporter: omegatype(a)gmail.com Hardware: Other Status: NEW Version: 10.2 Component: Drivers/Gallium/radeonsi Product: Mesa Created attachment 101986 --> https://bugs.freedesktop.org/attachment.cgi?id=101986&action=edit XOrg log Hello! After some time of work screen goes dark, than blinks and than hangs (picture stands still with no changes and no reaction on keyboard or mouse, numlock isn't working). # uname -a Linux 3.15.2-1-ARCH #1 SMP PREEMPT Fri Jun 27 07:41:19 CEST 2014 x86_64 GNU/Linux Mesa: 10.2.2-1 I have no specific options for radeon in /etc/X11/xorg.conf.d/*. XOrg.log end with messages like: (EE) [mi] EQ overflowing. Additional events will be discarded until existing events are processed. (EE) (EE) Backtrace: (EE) 0: /usr/bin/X (xorg_backtrace+0x48) [0x584b08] (EE) 1: /usr/bin/X (mieqEnqueue+0x22b) [0x566b7b] (EE) 2: /usr/bin/X (QueuePointerEvents+0x52) [0x44cc72] (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7fdd74bb3000+0x60ba) [0x7fdd74bb90ba] (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0x7fdd74bb3000+0x657d) [0x7fdd74bb957d] (EE) 5: /usr/bin/X (0x400000+0x72f08) [0x472f08] (EE) 6: /usr/bin/X (0x400000+0x9b4b0) [0x49b4b0] (EE) 7: /usr/lib/libpthread.so.0 (0x7fdd7ba3b000+0xf4b0) [0x7fdd7ba4a4b0] (EE) 8: /usr/lib/libc.so.6 (ioctl+0x7) [0x7fdd7a769e47] (EE) 9: /usr/lib/libdrm.so.2 (drmIoctl+0x28) [0x7fdd7b8329b8] (EE) 10: /usr/lib/libdrm.so.2 (drmCommandWrite+0x1b) [0x7fdd7b834c2b] (EE) 11: /usr/lib/libdrm_radeon.so.1 (0x7fdd74fc2000+0x2189) [0x7fdd74fc4189] (EE) 12: /usr/lib/xorg/modules/drivers/radeon_drv.so (0x7fdd751d0000+0x41b3a) [0x7fdd75211b3a] (EE) 13: /usr/lib/xorg/modules/drivers/radeon_drv.so (0x7fdd751d0000+0x42e00) [0x7fdd75212e00] (EE) 14: /usr/lib/libdrm.so.2 (drmHandleEvent+0x7e) [0x7fdd7b836e6e] (EE) 15: /usr/bin/X (WakeupHandler+0x6d) [0x43a59d] (EE) 16: /usr/bin/X (WaitForSomething+0x1bf) [0x5820bf] (EE) 17: /usr/bin/X (0x400000+0x359e1) [0x4359e1] (EE) 18: /usr/bin/X (0x400000+0x39aaa) [0x439aaa] (EE) 19: /usr/lib/libc.so.6 (__libc_start_main+0xf0) [0x7fdd7a6a8000] (EE) 20: /usr/bin/X (0x400000+0x2507e) [0x42507e] -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 56666] New: AMD SUMO GPU lockup when launching any heavy 3D application
by bugzilla-daemon＠freedesktop.org 25 Aug '18

25 Aug '18

https://bugs.freedesktop.org/show_bug.cgi?id=56666 Priority: medium Bug ID: 56666 Assignee: dri-devel(a)lists.freedesktop.org Summary: AMD SUMO GPU lockup when launching any heavy 3D application Severity: critical Classification: Unclassified OS: Linux (All) Reporter: runetmember(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI Created attachment 69423 --> https://bugs.freedesktop.org/attachment.cgi?id=69423&action=edit AMD SUMO GPU lockup when I launch Unigine Heaven 3 GPU lockup happen for me while launching any heavy 3D application on Radeon HD 6620G. For example GPU lockup 100% reproducible when I launch Unigine Heaven 3 (dmesg attached). It also may happen in web-browser, if browser use rendering hardware acceleration (for example Firefox with enabled "layers.acceleration.force-enabled" option). Lockup is not reproducible when I launch same applications on discrete Radeon HD 6650M GPU using DRI_PRIME feature, so I guess my issue related to AMD SUMO GPU's (or maybe to more APU's). Software: Kubuntu 12.10 x86_64 updated from Xorg Edgers PPA. Linux 3.7rc3. With Linux 3.5 and 3.6 is also reproducible, Mesa: 9.1~git20121029.00e6819e libdrm-radeon1: git20121025.bc494b31 xserver-xorg-video-radeon: git20120928.e8cb0b72 xserver-xorg-core: 1.13.0+git20120920.70e57668 KDE 4.9.2, desktop effects enabled. Hardware: Acer Aspire 7560G laptop, BIOS 2.04, AMD APU A8-3500M with integrated Radeon HD 6620G (SUMO) Discrete AMD Radeon HD 6650M (TURKS) -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 83748] New: Only black content on screen, in the Tokyo flashback of the game "The Secret World"
by bugzilla-daemon＠freedesktop.org 20 Jul '18

20 Jul '18

https://bugs.freedesktop.org/show_bug.cgi?id=83748 Priority: medium Bug ID: 83748 Assignee: dri-devel(a)lists.freedesktop.org Summary: Only black content on screen, in the Tokyo flashback of the game "The Secret World" Severity: normal Classification: Unclassified OS: Linux (All) Reporter: john.ettedgui(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/Gallium/radeonsi Product: Mesa Hey, I am trying to play the game "The Secret World" on my system. It is a Windows game so I am using Wine to run it. Initially the game runs, and I can see everything (cinematics and in-game stuff), but for some reason once I enter the Tokyo flashback, I cannot see the cinematic or anything in that dungeon. In the cinematic my screen seems to be completely black. Once back in-game, all content is dark/black, but I can kind of see where walls are or the overall shape of my character. Maybe that's what it would be with a null contrast and 0 brightness? Also the game is still running, I can interact with the npcs (if I manage to find them) etc... I tried using stable mesa 10.2.7 instead of daily git but it was the same. I then tried running the game on the same machine using the Catalyst drivers and all the visuals were there, both in the cinematic and in-game, so as far as I can see the issue shouldn't be in Wine. I don't understand why I'm getting that problem only in that part of the game, I've passed it using Catalyst, and now I'm able to continue the game normally with the gallium driver after this strange part... I am not sure what logs to add to this, since it is a visual issue and I don't see any kind of error message about it (although it could be hidden in the wine verbose logs I suppose). My system: Radeon 7970 running with Mesa, daily git or 10.2.7. llvm either daily git or 3.5.0 Arch Linux 64b with Linux kernel 3.16.2 I've tried both wine and wine-csmt, both have the same issue. Thanks! -- You are receiving this mail because: You are the assignee for the bug.

1 17

[Bug 69120] New: With dpm=1 vdpau is not usable
by bugzilla-daemon＠freedesktop.org 20 Jul '18

20 Jul '18

https://bugs.freedesktop.org/show_bug.cgi?id=69120 Priority: medium Bug ID: 69120 Assignee: dri-devel(a)lists.freedesktop.org Summary: With dpm=1 vdpau is not usable Severity: normal Classification: Unclassified OS: Linux (All) Reporter: john.ettedgui(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: 9.2 Component: Drivers/Gallium/r600 Product: Mesa Hello, with radeon.dpm=0 (or not set), vdpau output works very fine. But if I switch to radeon.dpm=1 it becomes unusable. mplayer tells me that my computer is too slow, video stutters to a crazy extent, same in xbmc. With dpm set to 1, I am still able to watch videos "normally" if not using vdpau. I have a Radeon 4670, Linux 3.11, Mesa 9.2 and Radeon 1:7.2.0. I tried to change power_dpm_state and power_dpm_force_performance_level to see if it would help. power_dpm_state stays at performance but even if I set power_dpm_force_performance_level to high, but it always reverts to auto... This doesn't help at all... I am not sure what else to attach. Thank you -- You are receiving this mail because: You are the assignee for the bug.

1 29

[PATCH wq#for-linus] drm: fix a fallout from slow-work -> wq conversion
by Tejun Heo 19 Jun '18

19 Jun '18

Commit 991ea75c (drm: use workqueue instead of slow-work), which made drm to use wq instead of slow-work, didn't account for the return value difference between delayed_slow_work_enqueue() and queue_delayed_work(). The former returns 0 on success and -errno on failures while the latter never fails and only uses the return value to indicate whether the work was already pending or not. This misconversion triggered spurious error messages. Remove the now unnecessary return value check and error message. Signed-off-by: Tejun Heo <tj(a)kernel.org> Reported-by: Markus Trippelsdorf <markus(a)trippelsdorf.de> Cc: David Airlie <airlied(a)linux.ie> Cc: dri-devel(a)lists.freedesktop.org --- Markus, it's almost trivial but it would be great if you can test this one too. David, may I route this wq#for-linus? Thanks. drivers/gpu/drm/drm_crtc_helper.c | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/drivers/gpu/drm/drm_crtc_helper.c b/drivers/gpu/drm/drm_crtc_helper.c index 4598130..211ed7e 100644 --- a/drivers/gpu/drm/drm_crtc_helper.c +++ b/drivers/gpu/drm/drm_crtc_helper.c @@ -839,7 +839,6 @@ static void output_poll_execute(struct work_struct *work) struct drm_connector *connector; enum drm_connector_status old_status, status; bool repoll = false, changed = false; - int ret; mutex_lock(&dev->mode_config.mutex); list_for_each_entry(connector, &dev->mode_config.connector_list, head) { @@ -874,11 +873,8 @@ static void output_poll_execute(struct work_struct *work) dev->mode_config.funcs->output_poll_changed(dev); } - if (repoll) { - ret = queue_delayed_work(system_nrt_wq, delayed_work, DRM_OUTPUT_POLL_PERIOD); - if (ret) - DRM_ERROR("delayed enqueue failed %d\n", ret); - } + if (repoll) + queue_delayed_work(system_nrt_wq, delayed_work, DRM_OUTPUT_POLL_PERIOD); } void drm_kms_helper_poll_disable(struct drm_device *dev)

4 4

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel September 2014