From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 100308] *ERROR* clock recovery reached max voltage
Date: Wed, 22 Mar 2017 03:49:59 +0000 [thread overview]
Message-ID: <bug-100308-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 4292 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=100308
Bug ID: 100308
Summary: *ERROR* clock recovery reached max voltage
Product: DRI
Version: DRI git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel@lists.freedesktop.org
Reporter: alex.c.liang@gmail.com
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
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 5672 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2017-03-22 3:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 3:49 bugzilla-daemon [this message]
2019-11-19 9:26 ` [Bug 100308] *ERROR* clock recovery reached max voltage bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-100308-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).