dri-devel October 2016

dri-devel@lists.freedesktop.org

215 participants
1390 discussions

[Bug 90926] Unusable GPU
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=90926 Bug ID: 90926 Summary: Unusable GPU Product: DRI Version: XOrg git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: blocker Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: artivision3(a)gmail.com Laptop with A6-6310 CPU and R5-M230 dedicated GPU. When using DRI_PRIME=1 the DGPU hangs in "power level 4" at 850mhz. It doesn't hang in "power level 0" at 300mhz. Disable DPM doesn't solve the problem. Disable Dynamic_Frequency_Scaling and start at 850mhz doesn't solve the problem. Kernel version, DRI version, Mesa version "Oibaf PPA or not", composition level (GL, XRender, or not), Apps 32-64bit, they don't make a difference. Everything hangs and so i cannot take terminal output from the almost all Apps. Wine hangs alone, but the terminal doesn't show any errors and then i have to close the terminal to kill Wine window. PCSX2 shows: radeon: size : 128 bytes radeon: alignment : 4096 bytes radeon: domains : 4 radeon: va : 0x000000000553a000 radeon: Failed to allocate virtual address for buffer: radeon: size : 128 bytes radeon: alignment : 4096 bytes radeon: domains : 4 radeon: va : 0x000000000553a000 radeon: Failed to allocate virtual address for buffer: radeon: size : 128 bytes radeon: alignment : 4096 bytes radeon: domains : 4 radeon: va : 0x000000000553a000 radeon: Failed to allocate virtual address for buffer: radeon: size : 128 bytes radeon: alignment : 4096 bytes radeon: domains : 4 radeon: va : 0x000000000553a000 Configuration: $ sudo cat /var/log/Xorg.0.log | grep -i dri3 [ 20.305] (**) RADEON(0): Option "DRI3" "on" [ 23.069] (**) RADEON(G0): Option "DRI3" "on" [ 23.076] (**) RADEON(G0): DRI3 enabled [ 23.210] (**) RADEON(0): DRI3 enabled $ xrandr --listproviders Providers: number : 3 Provider 0: id: 0x74 cap: 0x9, Source Output, Sink Offload crtcs: 2 outputs: 3 associated providers: 2 name:radeon Provider 1: id: 0x3f cap: 0x6, Sink Output, Source Offload crtcs: 0 outputs: 0 associated providers: 2 name:radeon Provider 2: id: 0x3f cap: 0x6, Sink Output, Source Offload crtcs: 0 outputs: 0 associated providers: 2 name:radeon $ DRI_PRIME=1 glxinfo | grep "OpenGL renderer" OpenGL renderer string: Gallium 0.4 on AMD HAINAN -- You are receiving this mail because: You are the assignee for the bug.

1 10

[Bug 90340] RADEON "PITCAIRN" displayport output breaks when monitor turned off and on
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=90340 Bug ID: 90340 Summary: RADEON "PITCAIRN" displayport output breaks when monitor turned off and on Product: DRI Version: XOrg 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: steve(a)einval.com As initially reporte in Debian at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783705 I'm running Debian Jessie (3.16.x kernel) on a machine with a Pitcairn-based video adapter and an NEC Multisync EA274WMi 27" monitor, connected via DisplayPort. I've also tried upgrading to the 4.0 kernel and I see exactly the same symptoms. If I turn the monitor off and then on again (as I was doing overnight), I get no display at all. I've wiggled the mouse, hit numlock on the keybard (the numlock led illuminates fine), etc., but no display. I've seen this kind of thing happen in the past on some machines, so I switch to VT1 and back to see if that helps. Still no display at all, either on console or under X. I log in remotely and I can see that the Xorg.0.log file has been updated with mode lines for the monitor, suggesting things have just woken up fine. But still no display. Here's the really weird thing: at this point, the monitor has basically locked up. It won't respond to the power/input/menu butttons at all, and is still showing the blue LED that says "I have signal" rather than switching to the amber "no signal" warning. Therefore, I can only assume there's a problem here with some weird invalid DP signal being produced. I've carried on playing with this. If I log in from another machine and run xrandr, I can see the display details of the monitor just fine. If I use xrandr to turn the display off and then on again: xrandr --output DisplayPort-0 --off xrandr --output DisplayPort-0 2560x1440 then things start working again. -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 90320] Lenovo ThinkPad E455 (Kaveri A10-7300): Blank built-in screen with radeon kms driver
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=90320 Bug ID: 90320 Summary: Lenovo ThinkPad E455 (Kaveri A10-7300): Blank built-in screen with radeon kms driver Product: DRI Version: DRI git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: blocker Priority: highest Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: sibradzic(a)gmail.com Created attachment 115550 --> https://bugs.freedesktop.org/attachment.cgi?id=115550&action=edit dmesg 4.1 rc1 As soon as the radeon kms switches in from efifb, the screen goes blank for the moment (no backlight), and then the backlight switches in, but the screen remains black. External HDMI output works just fine. No X is involved, I can't even see the kms console @ eDP. I can even control the backlight on the eDP display, but all i get is the various shades of black. Fglrx works fine, although it flickers wildly before the picture gets stable. I've tried numerous things, like forcing EDID that was grabbed from fglrx, disabling audio, applying all the DP training / backlight disabling patches as in https://bugs.freedesktop.org/show_bug.cgi?id=73530, all to no avail. Currently on linux 4.1rc1, tried 3.13, 3.16 & 3.19 as well, same issue. Please help! I bought this laptop cause I prefer AMD, and was expecting Lenovo to work great with Linux, but so far its broken. Ready to try some patches... -- You are receiving this mail because: You are the assignee for the bug.

1 23

[Bug 90291] X freeze/lockup out of nowhere
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=90291 Bug ID: 90291 Summary: X freeze/lockup out of nowhere Product: DRI Version: DRI git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: ancoron(a)chaoslayer.de Created attachment 115519 --> https://bugs.freedesktop.org/attachment.cgi?id=115519&action=edit Xorg.0.log of the crashed session I experienced a lockup/freeze without any specific reason. Operating system: Kubuntu 14.10 Linux Kernel: 3.19.0 libglamor version: 0.6.0+git20140801.347ef4f0-0ubuntu0sarvatt libdrm-radeon version: 2.4.60+git20150416.0d78b37b-0ubuntu0ricotz2~utopic xserver/radeon version: 7.4.99+git20140806.fbf575cb-0ubuntu0sarvatt3 MESA version: 10.6.0~git20150423.1 At the time of the hang I had started some rsync copying quite some data between two remote NFS mounts on different servers. When X freeze'd, the display went black and monitors turned into standby. Changing to another terminal was not possible, although keys like NumLock still reacted. In addition, all other processes - even foreground processes inside the X sessions' terminal windows - continued to run (like the rsync). The actual backtrace of the X freeze (debugging symbols where not installed up to now, sorry): (EE) 0: /usr/bin/X (xorg_backtrace+0x56) [0x7ff7b4c1c986] (EE) 1: /usr/bin/X (0x7ff7b4a66000+0x1bab69) [0x7ff7b4c20b69] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7ff7b2798000+0x36eb0) [0x7ff7b27ceeb0] (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (0x7ff7b2798000+0x98168) [0x7ff7b2830168] (EE) 4: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so (0x7ff7ac742000+0x16e7ce) [0x7ff7ac8b07ce] (EE) 5: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so (0x7ff7ac742000+0x16ebd2) [0x7ff7ac8b0bd2] (EE) 6: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so (0x7ff7ac742000+0x16f51a) [0x7ff7ac8b151a] (EE) 7: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so (0x7ff7ac742000+0x1c604f) [0x7ff7ac90804f] (EE) 8: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so (0x7ff7ac742000+0x1604fa) [0x7ff7ac8a24fa] (EE) 9: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so (0x7ff7ac742000+0x16076a) [0x7ff7ac8a276a] (EE) 10: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so (0x7ff7ac742000+0x160a78) [0x7ff7ac8a2a78] (EE) 11: /usr/lib/xorg/modules/libglamoregl.so (0x7ff7ade2a000+0x223e4) [0x7ff7ade4c3e4] (EE) 12: /usr/lib/xorg/modules/libglamoregl.so (0x7ff7ade2a000+0x225d2) [0x7ff7ade4c5d2] (EE) 13: /usr/lib/xorg/modules/libglamoregl.so (0x7ff7ade2a000+0x13b31) [0x7ff7ade3db31] (EE) 14: /usr/lib/xorg/modules/libglamoregl.so (0x7ff7ade2a000+0x13f0a) [0x7ff7ade3df0a] (EE) 15: /usr/bin/X (0x7ff7b4a66000+0x140103) [0x7ff7b4ba6103] (EE) 16: /usr/bin/X (0x7ff7b4a66000+0x53cd0) [0x7ff7b4ab9cd0] (EE) 17: /usr/bin/X (0x7ff7b4a66000+0x57077) [0x7ff7b4abd077] (EE) 18: /usr/bin/X (0x7ff7b4a66000+0x5b286) [0x7ff7b4ac1286] (EE) 19: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf5) [0x7ff7b27b9ec5] (EE) 20: /usr/bin/X (0x7ff7b4a66000+0x456ae) [0x7ff7b4aab6ae] (EE) (EE) Bus error at address 0x7ff7b4914000 (EE) Fatal server error: (EE) Caught signal 7 (Bus error). Server aborting -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 90263] GPU card fans run full speed at all times
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=90263 Bug ID: 90263 Summary: GPU card fans run full speed at all times Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: todd(a)todddailey.ca Arch w/ Linux 4. AMD "6770" "BARTS" GPU. GPU fans run at full speed at all times. Lots of promises on the forums that the fix would "just work" in Linux 4. It did not. Not an issue when dual-booted to Windows 7. Fans run properly. -- You are receiving this mail because: You are the assignee for the bug.

1 23

[Bug 90076] Random screen lockups
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=90076 Bug ID: 90076 Summary: Random screen lockups Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: nicolamori(a)aol.com Created attachment 115164 --> https://bugs.freedesktop.org/attachment.cgi?id=115164&action=edit dmesg I experience random lockups of the screen. The screen goes black then sometimes the image is back but frozen, sometimes it stays black. I can't do anything but a hard reset. It happens randomly when using KDE4 desktop and common applications (eclipse, firefox etc.). I did not notice any correlation with any particular usage pattern or application. I have DPM enabled. I attach the significant part of journaclt log recovered after reboot. Hardware: Mobility Radeon HD3470 (RV620) System: ArchLinux x86_64 Packages: linux 3.19.4 with ck patchset, xf86-video-ati 1:7.5.0, mesa 10.5.3 -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 90040] Using VDPAU in radeon breaks suspend to RAM, and caused BSoD
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=90040 Bug ID: 90040 Summary: Using VDPAU in radeon breaks suspend to RAM, and caused BSoD Product: DRI Version: XOrg git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: mail(a)3v1n0.net Created attachment 115086 --> https://bugs.freedesktop.org/attachment.cgi?id=115086&action=edit BSoD: [TTM] radeon failed to fill cached pool (r:-12)! If I use vdpau (both directly and via vdpau-va-driver), after that I watch some videos, my laptop hangs while suspending (and this happens always, after that I opened a certain number of videos). I'm using 3.0 Mesa 10.6.0-devel (10.6.0~git20150318) on kernel 3.16.0-34-generic. My radeon card is: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Madison [Mobility Radeon HD 5650] While generally this just leads to a frozen system, with no output, once I got a BSoD (really, on linux!??) as you can see in the attached picture, saying: [TTM] radeon 0000:01:00.0: Failed to fill cached pool (r:-12)! :00:16.0: request_threaded_ir failed: irq = 43 returns -12 me async: error -12 -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 89965] CAYMAN DRI_PRIME The Cave error: radeon: The kernel rejected CS
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=89965 Bug ID: 89965 Summary: CAYMAN DRI_PRIME The Cave error: radeon: The kernel rejected CS 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: frederic.romagne(a)gmail.com Created attachment 114980 --> https://bugs.freedesktop.org/attachment.cgi?id=114980&action=edit dmesg after the error When running The Cave through steam, using DRI_PRIME=1 steam The games freezes and corrupts the steam window. While I close the game, I cannot run anything with DRI_PRIME anymore, a message is spammed in the terminal: radeon: The kernel rejected CS, see dmesg for more information. I have a fresh git xf86-video-ati xf86-video-intel mesa and libdrm on kernel-3.19.3 Radeon 9650 and intel ivybridge 2500 -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 89916] DRI PRIME renders only black window
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=89916 Bug ID: 89916 Summary: DRI PRIME renders only black window 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: towo(a)siduction.org a have a Lenovo Notebook which contains a FX-7500. There are 2 graphics devices in: root@lenovo-nb:/home/towo# lspci | egrep -i "displ|vga" 00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R6/R7 Graphics] 01:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Jet PRO [Radeon R5 M230] (rev ff) The system is using the Kaveri graphics. towo:lenovo-nb> glxinfo | grep "OpenGL renderer string" OpenGL renderer string: Gallium 0.4 on AMD KAVERI towo:lenovo-nb> xrandr --listproviders Providers: number : 2 Provider 0: id: 0x86 cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload crtcs: 4 outputs: 3 associated providers: 1 name:radeon Provider 1: id: 0x4f cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload crtcs: 0 outputs: 0 associated providers: 1 name:radeon both devices are listed. xrandr --setprovideroffloadsink 0x4f 0x86 towo:lenovo-nb> DRI_PRIME=1 glxinfo | grep "renderer string" OpenGL renderer string: Gallium 0.4 on AMD HAINAN seems to work correct. DRI_PRIME=1 glxgears shows only a black window, but the fps are shown in the terminal, i start from. towo:lenovo-nb> LIBGL_DEBUG=verbose DRI_PRIME=1 glxgears libGL: screen 0 does not appear to be DRI3 capable libGL: pci id for fd 4: 1002:6665, driver radeonsi libGL: OpenDriver: trying /usr/lib/x86_64-linux-gnu/dri/tls/radeonsi_dri.so libGL: OpenDriver: trying /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so Running synchronized to the vertical refresh. The framerate should be approximately the same as the monitor refresh rate. 8793 frames in 5.0 seconds = 1758.569 FPS doesn't even give any error, but the windows stayes black. I use xfce 4.12 and have tryed 3 different compositors, with all i get the same black window. Resizing the windows does not help (that i read in many bug reports). kernel is 4.0.0-rc6, xserver is 1.16.4, mesa is 10.6-git and radeon driver is 7.5.0 There are zero errors in the terminal or logfiles. -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 89858] Radeon GPU lockup in Euro Truck Simulator 2
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=89858 Bug ID: 89858 Summary: Radeon GPU lockup in Euro Truck Simulator 2 Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: xorgbreaker(a)gmail.com Created attachment 114796 --> https://bugs.freedesktop.org/attachment.cgi?id=114796&action=edit Radeon GPU lockup When playing Euro Truck Simulator 2 by using Wine 1.7.39, system freezes and becomes unusable. I can only use the Magic SysRq "K" and reboot, because VT switch is not possible after lockup. My system takes a while to shutdown after that. In fact, in many games my experience is worst, a bit better when I use an older kernel, like the LTS 3.14.37. Software used: - Linux kernel: 3.19.3-1-ck - Mesa: 10.5.1 - Radeon driver (xf86-video-ati): 7.5.0 - X Server: 1.17.1 - Distro: Arch Linux x86_64 Hardware used: - Sapphire Radeon HD 6870 -- You are receiving this mail because: You are the assignee for the bug.

1 1

← Newer
1
...
6
7
8
9
10
11
12
...
139
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel October 2016