linux-kernel - [drm:radeon_dp_link_train] *ERROR* clock recovery failed

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20160303023811.GA31411@milliways>
Date:	Thu, 3 Mar 2016 02:38:11 +0000
From:	Ken Moffat <zarniwhoop@...world.com>
To:	linux-kernel@...r.kernel.org
Subject: [drm:radeon_dp_link_train] *ERROR* clock recovery failed

One of my machines is an A10 Kaveri desktop, with a good old VGA
connection to the monitor.  I've only just started trying to boot
any 4.5 kernel on it, but with 4.5.0-rc6 and now linus's tree from a
few hours ago (4.5.0-rc6-00018-gf983cd3) I get a blank screen, with
no video signal, as soon as it tries to switch to a framebuffer.

Comparing the logs, the first bad attempt had a couple of new error
messages, everything else in the logs looked normal -

Mar  1 19:31:10 deluxe kernel: [    2.543163] fbcon: radeondrmfb (fb0) is primary device
Mar  1 19:31:10 deluxe kernel: [    2.654179] [drm:radeon_dp_link_train] *ERROR* clock recovery reached max voltage
Mar  1 19:31:10 deluxe kernel: [    2.654181] [drm:radeon_dp_link_train] *ERROR* clock recovery failed
Mar  1 19:31:10 deluxe kernel: [    2.677142] Console: switching to colour frame buffer device 200x56
Mar  1 19:31:10 deluxe kernel: [    2.680435] radeon 0000:00:01.0: fb0: radeondrmfb frame buffer device

Any suggestions where to start looking, please ?

ĸen
-- 
This email was written using 100% recycled letters.