Bug 100949

Can you bisect?

Created attachment 131255 [details]
dmesg sorted by drm

dmesg sorted by drm attached, Noticeable problems are

[   28.135157] [drm] Internal thermal controller without fan control

[ 9815.904855] [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* displayport link status failed
[ 9815.904891] [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* clock recovery failed


Narrowing down to amdgpu which detailed the hardware
$ dmesg | grep amdgpu
[   23.120326] [drm] amdgpu kernel modesetting enabled.
[   23.618949] fb: switching to amdgpudrmfb from EFI VGA
[   23.619716] amdgpu 0000:00:01.0: VM size (-1) must be a power of 2
[   23.619975] amdgpu 0000:00:01.0: VRAM: 1024M 0x0000000000000000 - 0x000000003FFFFFFF (1024M used)
[   23.619977] amdgpu 0000:00:01.0: GTT: 3072M 0x0000000040000000 - 0x00000000FFFFFFFF
[   23.620094] [drm] amdgpu: 1024M of VRAM memory ready
[   23.620095] [drm] amdgpu: 3072M of GTT memory ready.
[   23.721480] amdgpu 0000:00:01.0: amdgpu: using MSI.
[   23.721510] [drm] amdgpu: irq initialized.
[   23.721519] [drm] amdgpu: dpm initialized
[   23.724341] [drm] amdgpu atom DIG backlight initialized
[   24.430744] amdgpu 0000:00:01.0: fence driver on ring 0 use gpu addr 0x0000000040000010, cpu addr 0xffffa02179c2d010
[   24.430790] amdgpu 0000:00:01.0: fence driver on ring 1 use gpu addr 0x0000000040000020, cpu addr 0xffffa02179c2d020
[   24.430843] amdgpu 0000:00:01.0: fence driver on ring 2 use gpu addr 0x0000000040000030, cpu addr 0xffffa02179c2d030
[   24.430921] amdgpu 0000:00:01.0: fence driver on ring 3 use gpu addr 0x0000000040000040, cpu addr 0xffffa02179c2d040
[   24.430971] amdgpu 0000:00:01.0: fence driver on ring 4 use gpu addr 0x0000000040000050, cpu addr 0xffffa02179c2d050
[   24.431066] amdgpu 0000:00:01.0: fence driver on ring 5 use gpu addr 0x0000000040000060, cpu addr 0xffffa02179c2d060
[   24.431123] amdgpu 0000:00:01.0: fence driver on ring 6 use gpu addr 0x0000000040000070, cpu addr 0xffffa02179c2d070
[   24.431170] amdgpu 0000:00:01.0: fence driver on ring 7 use gpu addr 0x0000000040000080, cpu addr 0xffffa02179c2d080
[   24.431221] amdgpu 0000:00:01.0: fence driver on ring 8 use gpu addr 0x0000000040000090, cpu addr 0xffffa02179c2d090
[   24.761420] amdgpu 0000:00:01.0: fence driver on ring 9 use gpu addr 0x00000000400000a0, cpu addr 0xffffa02179c2d0a0
[   24.761749] amdgpu 0000:00:01.0: fence driver on ring 10 use gpu addr 0x00000000400000b0, cpu addr 0xffffa02179c2d0b0
[   24.900778] amdgpu 0000:00:01.0: fence driver on ring 11 use gpu addr 0x000000000068cd30, cpu addr 0xffffb70d02238d30
[   24.993027] amdgpu 0000:00:01.0: fence driver on ring 12 use gpu addr 0x00000000400000d0, cpu addr 0xffffa02179c2d0d0
[   24.993099] amdgpu 0000:00:01.0: fence driver on ring 13 use gpu addr 0x00000000400000e0, cpu addr 0xffffa02179c2d0e0
[   26.092550] fbcon: amdgpudrmfb (fb0) is primary device
[   27.935642] amdgpu 0000:00:01.0: fb0: amdgpudrmfb frame buffer device
[   27.956506] [drm] Initialized amdgpu 3.16.0 20150101 for 0000:00:01.0 on minor 0
[   27.956682] amdgpu 0000:01:00.0: enabling device (0000 -> 0003)
[   27.957234] amdgpu 0000:01:00.0: VM size (-1) must be a power of 2
[   28.041269] amdgpu 0000:01:00.0: VRAM: 2048M 0x0000000000000000 - 0x000000007FFFFFFF (2048M used)
[   28.041274] amdgpu 0000:01:00.0: GTT: 3072M 0x0000000080000000 - 0x000000013FFFFFFF
[   28.041370] [drm] amdgpu: 2048M of VRAM memory ready
[   28.041372] [drm] amdgpu: 3072M of GTT memory ready.
[   28.042108] amdgpu 0000:01:00.0: PCIE GART of 3072M enabled (table at 0x0000000000040000).
[   28.042308] amdgpu 0000:01:00.0: amdgpu: using MSI.
[   28.042355] [drm] amdgpu: irq initialized.
[   28.135174] [drm] amdgpu: dpm initialized
[   28.265927] amdgpu 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000080000010, cpu addr 0xffffa0217c2eb010
[   28.266183] amdgpu 0000:01:00.0: fence driver on ring 1 use gpu addr 0x0000000080000020, cpu addr 0xffffa0217c2eb020
[   28.266262] amdgpu 0000:01:00.0: fence driver on ring 2 use gpu addr 0x0000000080000030, cpu addr 0xffffa0217c2eb030
[   28.266352] amdgpu 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000080000040, cpu addr 0xffffa0217c2eb040
[   28.266546] amdgpu 0000:01:00.0: fence driver on ring 4 use gpu addr 0x0000000080000050, cpu addr 0xffffa0217c2eb050
[   28.266982] [drm] enabling PCIE gen 3 link speeds, disable with amdgpu.pcie_gen2=0
[   30.289599] [drm] Initialized amdgpu 3.16.0 20150101 for 0000:01:00.0 on minor 1
[   30.485628] audit: type=1130 audit(1494213691.999:65): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-backlight@backlight:amdgpu_bl0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 3115.901737] [drm] enabling PCIE gen 3 link speeds, disable with amdgpu.pcie_gen2=0
[ 3117.273936] amdgpu 0000:01:00.0: PCIE GART of 3072M enabled (table at 0x0000000000040000).
[ 3136.430662] [drm] enabling PCIE gen 3 link speeds, disable with amdgpu.pcie_gen2=0
[ 3137.813144] amdgpu 0000:01:00.0: PCIE GART of 3072M enabled (table at 0x0000000000040000).
[ 9810.613716] [drm] enabling PCIE gen 3 link speeds, disable with amdgpu.pcie_gen2=0
[ 9811.994909] amdgpu 0000:01:00.0: PCIE GART of 3072M enabled (table at 0x0000000000040000).
[ 9815.206164] [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* displayport link status failed
[ 9815.206197] [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* clock recovery failed
[ 9815.904855] [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* displayport link status failed
[ 9815.904891] [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* clock recovery failed
[ 9815.982844] [drm] enabling PCIE gen 3 link speeds, disable with amdgpu.pcie_gen2=0
[ 9817.339313] amdgpu 0000:01:00.0: PCIE GART of 3072M enabled (table at 0x0000000000040000).

Hope the information is useful

I'm seeing the same *ERROR* lines on suspend/resume on one of my laptops, and the laptop panel stays black. Does that match your problem, or what did you mean by "broke the handling of power management"?

> I'm seeing the same *ERROR* lines on suspend/resume on one of my laptops, and 
> the laptop panel stays black. Does that match your problem, or what did you 
> mean by "broke the handling of power management"?

For the former, that matches the problem I encountered. 
About the line "broke the handling of power management", I noticed more fan noise than usual but it may be something else. It will be nice to optimize that power management if possible.

And you're saying suspend/resume broke around May 2nd for you? Do you happen to remember a commit before that where it worked for you?

Last commit that worked prior to the breakage was on 20170410. I just updated to the recent 20170511 which seems partially resolving the issue but the error message below still remains.

[22328.935171] [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* displayport link status failed
[22328.935217] [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* clock recovery failed

I'm still unclear as to the symptoms you're seeing. E.g., are the *ERROR* messages always accompanied by a black laptop panel? And does this only happen on suspend/resume, or also under other circumstances?

Yes, those *ERROR* message happened on suspend/resume followed by the black screen. Same errors also occurred when leaving the laptop in idle for a while as well.

Thanks for the clarification. Sounds like it's the same issue I'm seeing.

The XF86-video-ati driver is probably used. Kaveri does not work with this driver via DP. I have a black screen too.

I no longer own Asus X550Z which broke few months ago, replaced by HP Envy x360 Ryzen 2500U 15 inch. Feel free to continue or close this report.

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/163.