dri-devel August 2015

dri-devel@lists.freedesktop.org

178 participants
1142 discussions

[Bug 91375] [radeonsi] [drm:si_dpm_set_power_state [radeon]] *ERROR* si_restrict_performance_levels_before_switch failed
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=91375 Bug ID: 91375 Summary: [radeonsi] [drm:si_dpm_set_power_state [radeon]] *ERROR* si_restrict_performance_levels_before_switch failed Product: DRI Version: DRI git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: alexandre.f.demers(a)gmail.com [drm:si_dpm_set_power_state [radeon]] *ERROR* si_restrict_performance_levels_before_switch failed I just found out there is this message at boot. Using latest ddx, mesa and drm from git combined with a 4.1 kernel. I don't see any impact or side effect. As always, using a R9 280X. -- You are receiving this mail because: You are the assignee for the bug.

1 14

[Bug 91221] UVD: GPU lockup with BARTS
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=91221 Bug ID: 91221 Summary: UVD: GPU lockup with BARTS Product: DRI Version: XOrg git Hardware: All OS: All Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: chithanh(a)gentoo.org Created attachment 116935 --> https://bugs.freedesktop.org/attachment.cgi?id=116935&action=edit dmesg with drm.debug=14 When playing back a video using VDPAU and UVD it first plays fine, but the X Server reproducibly hangs after a few minutes. Audio will continue to play, but no screen updates will happen any more, nor is there any reaction to keyboard input. I have to use Magic SysRq to switch to the console and kill the X server. From that point on no acceleration will work, and the video card fan gets audibly louder, until the system is rebooted. When using Xv and no hardware decode acceleration, the video plays back fine. This is using Linux kernel 4.1.1 and Mesa 10.3.7. Hardware is In dmesg, messages like [ 1406.489288] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000031828 last fence id 0x000000000003182a on ring 0) [ 1406.919692] [drm:rv770_stop_dpm] *ERROR* Could not force DPM to low. [ 1407.091325] radeon 0000:01:00.0: couldn't schedule ib [ 1407.091329] [drm:radeon_uvd_suspend] *ERROR* Error destroying UVD (-22)! are shown. Nothing unusual in the Xorg.0.log. -- You are receiving this mail because: You are the assignee for the bug.

1 9

[Bug 91197] Radeon Trinity 7400G fails with 4K UHD screen - atombios stuck exeuting BF64
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=91197 Bug ID: 91197 Summary: Radeon Trinity 7400G fails with 4K UHD screen - atombios stuck exeuting BF64 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: dennis.jansen(a)web.de I have several issues trying to connect a 4k display to the radeon card via HDMI (@30Hz). If I boot with the screen connected, when trying to take over modesetting from EFI, the internal notebook display goes black as well as the external. When I try to attach it during runtime, I can see the 3840 mode, but when I tryt to select it I get [ 97.667521] [drm:atom_op_jump [radeon]] *ERROR* atombios stuck in loop for more than 5secs aborting [ 97.667549] [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing BF64 (len 962, WS 0, PS 0) @ 0xC1A1 Switching back to 1920 works fine, trying again simply causes the same error again. Tested Linux kernels 4.1.0 and 3.19. Ubuntu 15.04. I might not be able to test for long, will probably send the screen back before long if I can't get it working in full resolution at all. -- You are receiving this mail because: You are the assignee for the bug.

1 20

[Bug 91192] ring test failed/si startup failed on resume
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=91192 Bug ID: 91192 Summary: ring test failed/si startup failed on resume Product: Mesa Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 Assignee: dri-devel(a)lists.freedesktop.org Reporter: benjo316_2003(a)yahoo.com QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 116879 --> https://bugs.freedesktop.org/attachment.cgi?id=116879&action=edit journalctl output and kernel bug After resume from suspend, upon adjusting the volume (and once without adjusting the volume), window controls become unresponsive for long periods (>15s) and audio dies. After the each unresponsive period, some input events (clicks, etc.) begin catching up and new events are allowed until the next period. The only way to restore everything to normal (afaik) is to log out and in again. One time I did this, and it triggered a kernel BUG (see attachment 'journal.txt'). journal2.txt is from when it happened without changing the volume. System Info: ArchLinux (*-testing + lcarlier mesa-git enabled) Linux version 4.0.7-2 Command-line: root=PARTUUID=7ea06983-7065-4692-aa21-82645fd721ee ro radeon.dpm=1 drm.rnodes=1 Mesa version: 70936.aa7d4ce-1 Xorg ati driver ver: 3233.afab783-1 DE: Plasma-desktop 5.3.2-1 I will be away from my computer for a couple weeks, but if you have any questions I'll try to answer as best I can. -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 91084] RadeonSI crash while playing World Of Tanks
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=91084 Bug ID: 91084 Summary: RadeonSI crash while playing World Of Tanks 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: edzis(a)inbox.lv Computer freezes completely however I can access it via the ssh. Versions are in the files. This is with Ubuntu 14.04 using liquorix kernel and this is the first time I can actually ssh into the machine after crash. Previously tried with Ubuntu 15.04 using kernel 4.1/3.13/3.19/4.0.x all of them crash completely. Versions/syslog/etc. are in the attachments. Please ask if You need more info. -- You are receiving this mail because: You are the assignee for the bug.

1 15

[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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel August 2015