Created attachment 128297 [details] dmesg My laptop has an Intel CPU/iGPU + AMD dGPU I compiled both the current master of 4.9 and drm-next-4.10-wip, I have the same problem, when I try to use the m265x with "DRI_PRIME=1 glxgears" everything freezes for about 5~10 seconds, then glxgears appears but the gears are either frozen or I just get a black window. Then when I try to shutdown it never completely turn off and I have to force the power off I tried both with and without amdgpu.runpm=0 but I get the same behaviour.
Created attachment 128298 [details] Xorg log
Created attachment 129431 [details] dmesg when glxgears runs once Small update, on drm-next-4.11-wip sometimes glxgears starts correctly the first time, but it freezes on subsequent runs. On dmesg I get: asynchronous wait on fence amd_sched:gfx:19 timed out Full dmesg attached
I can confirm this bug also. Hardware: 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Opal XT [Radeon R7 M265] (rev 81) Subsystem: Hewlett-Packard Company Device 814f Kernel driver in use: amdgpu Kernel modules: radeon, amdgpu My dmesg error is mildly different though: [ 156.940353] amdgpu 0000:03:00.0: PCIE GART of 1024M enabled (table at 0x0000000000040000). [ 157.159282] [drm] ring test on 0 succeeded in 9 usecs [ 157.161319] [drm] ring test on 1 succeeded in 1 usecs [ 157.161331] [drm] ring test on 2 succeeded in 1 usecs [ 157.161346] [drm] ring test on 3 succeeded in 3 usecs [ 157.161355] [drm] ring test on 4 succeeded in 4 usecs [ 168.384040] asynchronous wait on fence amd_sched:gfx:13 timed out Also tested with glxgears. Doing so crashes the application into a state it cannot be killed in, and often also takes down the rest of the system by freezing the entire gui.
The GPU now works with AMDGPU driver on latest linux master. Playing some Rocket League I had a couple of crashes, but the game was just updated so I don't know if it was the kernel. Anyways, marking as fixed as it works now.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.