Bug 100308

Summary:	ERROR clock recovery reached max voltage
Product:	DRI	Reporter:	alex.c.liang
Component:	DRM/Radeon	Assignee:	Default DRI bug account <dri-devel>
Status:	RESOLVED MOVED	QA Contact:
Severity:	normal
Priority:	medium	CC:	alex.c.liang
Version:	DRI git
Hardware:	x86-64 (AMD64)
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:

Description alex.c.liang 2017-03-22 03:49:59 UTC

The following starting happening after upradeing to xf86-video-ati-1:7.9.0-1-x86_64.pkg.tar.xz on arch linux. (ALL Monitors go blank) First thought it was kernel and tried rolling back a few versions and was still happening. On the new kernel versions it just happens ramdonly. On the older kernels it only happens when trying to wake monitors. It's always the following errors.

Mar 18 10:05:00 showdownarch kernel: [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery reached max voltage
Mar 18 10:05:00 showdownarch kernel: [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed


I've switched to AMDGPU since it now has experimental support for southern islands. 

Thx much for the hardwork!!!!



stack trace...
------------[ cut here ]------------
Mar 18 10:05:00 showdownarch kernel: WARNING: CPU: 3 PID: 13100 at ./include/drm/drm_crtc.h:1403 drm_helper_choose_encoder_dpms+0x8a/0x90 [drm_kms_helper]
Mar 18 10:05:00 showdownarch kernel: Modules linked in: xt_multiport iptable_filter overlay snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi iTCO_wdt gpio_ich iTCO_ven
Mar 18 10:05:00 showdownarch kernel:  mii fb_sys_fops i2c_algo_bit button snd_timer snd mei_me soundcore mei intel_agp shpchp intel_gtt acpi_cpufreq tpm_tis tpm_tis_core tpm sch_fq_
Mar 18 10:05:00 showdownarch kernel: CPU: 3 PID: 13100 Comm: kworker/3:256 Tainted: G        W       4.9.14-1-lts #1
Mar 18 10:05:00 showdownarch kernel: Hardware name: Gigabyte Technology Co., Ltd. H55-USB3/H55-USB3, BIOS F7 08/20/2010
Mar 18 10:05:00 showdownarch kernel: Workqueue: events radeon_dp_work_func [radeon]
Mar 18 10:05:00 showdownarch kernel:  ffffc90010d63d20 ffffffff812f890d 0000000000000000 0000000000000000
Mar 18 10:05:00 showdownarch kernel:  ffffc90010d63d60 ffffffff8107cb0b 0000057b9e861d09 ffff88030a843000
Mar 18 10:05:00 showdownarch kernel:  ffff88030ffe7a00 ffff88030f5f9000 0000000000000003 ffff88030aa92660
Mar 18 10:05:00 showdownarch kernel: Call Trace:
Mar 18 10:05:00 showdownarch kernel:  [<ffffffff812f890d>] dump_stack+0x63/0x86
Mar 18 10:05:00 showdownarch kernel:  [<ffffffff8107cb0b>] __warn+0xcb/0xf0
Mar 18 10:05:00 showdownarch kernel:  [<ffffffff8107cc3d>] warn_slowpath_null+0x1d/0x20
Mar 18 10:05:00 showdownarch kernel:  [<ffffffffa044408a>] drm_helper_choose_encoder_dpms+0x8a/0x90 [drm_kms_helper]
Mar 18 10:05:00 showdownarch kernel:  [<ffffffffa04444eb>] drm_helper_connector_dpms+0x4b/0x100 [drm_kms_helper]
Mar 18 10:05:00 showdownarch kernel:  [<ffffffffa04465cb>] ? drm_dp_dpcd_read_link_status+0x1b/0x20 [drm_kms_helper]
Mar 18 10:05:00 showdownarch kernel:  [<ffffffffa05ab477>] radeon_connector_hotplug+0xf7/0x100 [radeon]
Mar 18 10:05:00 showdownarch kernel:  [<ffffffffa05b91ff>] radeon_dp_work_func+0x3f/0x60 [radeon]
Mar 18 10:05:00 showdownarch kernel:  [<ffffffff81096399>] process_one_work+0x1e9/0x440
Mar 18 10:05:00 showdownarch kernel:  [<ffffffff8109663b>] worker_thread+0x4b/0x4f0
Mar 18 10:05:00 showdownarch kernel:  [<ffffffff810965f0>] ? process_one_work+0x440/0x440
Mar 18 10:05:00 showdownarch kernel:  [<ffffffff8109c0c9>] kthread+0xd9/0xf0
Mar 18 10:05:00 showdownarch kernel:  [<ffffffff8102c74e>] ? __switch_to+0x2ce/0x5b0
Mar 18 10:05:00 showdownarch kernel:  [<ffffffff8109bff0>] ? kthread_park+0x60/0x60
Mar 18 10:05:00 showdownarch kernel:  [<ffffffff815f8a55>] ret_from_fork+0x25/0x30
Mar 18 10:05:00 showdownarch kernel: ---[ end trace 6a290eae4410f871 ]---
Mar 18 10:05:00 showdownarch kernel: [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery reached max voltage
Mar 18 10:05:00 showdownarch kernel: [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed

Comment 1 Martin Peres 2019-11-19 09:26:53 UTC

-- 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/787.

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.