| Summary: | Hotplugging DP1.2 monitor(s) causes machine to hang waiting for page flip | ||||||
|---|---|---|---|---|---|---|---|
| Product: | DRI | Reporter: | Robert Straw <hime> | ||||
| Component: | DRM/AMDgpu | Assignee: | Default DRI bug account <dri-devel> | ||||
| Status: | RESOLVED MOVED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | medium | CC: | harry.wentland, nicholas.kazlauskas | ||||
| Version: | unspecified | ||||||
| Hardware: | x86-64 (AMD64) | ||||||
| OS: | Linux (All) | ||||||
| Whiteboard: | |||||||
| i915 platform: | i915 features: | ||||||
| Attachments: |
|
||||||
I was going to attempt to bisect this tonight: however on a lark I decided to try 4.20-rc6 as it is nearing completion. I am pleased to report that I am *not* seeing this issue on 4.20-rc6. I suspect that the kernel commit a81a7c9 which loads polaris11_k_mc.bin (which I got from here[1]) for my particular card may have fixed the issue. [1]: https://people.freedesktop.org/~agd5f/radeon_ucode/ -- 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/644. |
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.
Created attachment 142774 [details] dmesg: DRM call stack Greetings, I am using kernel 4.19.8, I have two 4K panels which have DP1.2 inputs as well as an AMD RX560 GPU[1]. I am experiencing an issue where my machine softlocks when they are disconnected & subsequently reconnected. If the monitors are power-cycled ,or the DP cable is hotplugged, my kernel log slowly accumulates messages like "*ERROR* [PLANE:36:plane-0] flip_done timed out" meanwhile my graphical environment hangs, waiting for the pageflip which never successfully happens. One of my monitors also happens be HDMI2.0 capable, and when connected via HDMI that monitor *does not* lock up the machine in this way, so I believe this issue to be DisplayPort specific. Attached is a dmesg from a recent session exhibiting such a softlock, the relevant portions are near the end. All my softlocks have `RIP: 0010:prepare_flip_isr+0x5f/0x70 [amdgpu]` in common. I will note that the driver does seem to at least partially initialize the monitors upon reconnection, as they do not display "no signal" nor enter sleep mode. [1]: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 550 640SP / RX 560/560X] [1002:67ff] (rev cf)