Bug 1391676 - lockscreen freeze amdgpu displayport link status failed
Summary: lockscreen freeze amdgpu displayport link status failed
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-amdgpu
Version: 26
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Christopher Atherton
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-03 18:19 UTC by Ralph Giles
Modified: 2017-07-26 21:49 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-07-26 21:49:13 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Ralph Giles 2016-11-03 18:19:22 UTC
Description of problem:

I come back to my desktop and the lockscreen is up (monitors not asleep) but frozen and unresponsive. No mouse pointer, no response to keyboard <enter>, <ctrl-alt-F3>, etc. Machine is accessible over ssh and otherwise fine.

Version-Release number of selected component (if applicable):

Up-to-date Fedora Workstation 25 (beta) on Lenovo P710 with Radeon RX480, three displays.

How reproducible:

Happened twice today. I don't know how to trigger it.

Steps to Reproduce:
1. boot system
2. log in
3. wait? :/

Actual results:

Lock screen unresponsive.

Expected results:

Screens stay asleep until input is detected, then lockscreen transitions to login prompt.

Additional info:

journalctl says from the time of the freeze:

Nov 03 10:03:24 nanger kernel: [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* displayport link status failed
Nov 03 10:03:24 nanger kernel: [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* clock recovery failed
Nov 03 10:03:24 nanger kernel: [drm:amdgpu_crtc_page_flip [amdgpu]] *ERROR* failed to get vblank before flip

Comment 1 Ralph Giles 2016-11-03 18:19:51 UTC
This is Fedora 25, so it's using wayland instead of X; not sure xorg-x11-drv-amdgpu is the correct component.

Comment 2 Ralph Giles 2016-11-09 18:52:27 UTC
Happened again Tuesday on 4.8.6-300.fc25.x86_64.

Comment 3 Ralph Giles 2016-11-14 21:44:05 UTC
Happened again today on 4.8.6-300.fc25.x86_64.

Comment 4 Ralph Giles 2016-11-17 01:14:34 UTC
Also happens with 4.8.7-300.fc25.x86_64.

Comment 5 Ralph Giles 2016-11-25 23:03:11 UTC
And with 4.8.8-300.fc25.x86_64.

I wonder if this is related to bug 1392119. I haven't been able to reproduce it if I turn off all but one display before the lock screen engages.

Comment 6 Ralph Giles 2016-12-12 20:47:49 UTC
Happened today with 4.8.12-300.fc25.x86_64.

Comment 7 Ralph Giles 2017-01-30 23:07:54 UTC
This still occurs occasionally, but not as frequently as it did earlier.

Comment 8 Fedora End Of Life 2017-02-28 10:33:23 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle.
Changing version to '26'.

Comment 9 Ralph Giles 2017-07-26 21:49:13 UTC
I haven't seen this recently. Closing.


Note You need to log in before you can comment on or make changes to this bug.