<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Freezes on Trinity 7500G" href="https://bugs.freedesktop.org/show_bug.cgi?id=67713#c9">Comment # 9</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Freezes on Trinity 7500G" href="https://bugs.freedesktop.org/show_bug.cgi?id=67713">bug 67713</a> from <a class="email" href="mailto:ekoleszar@gmail.com" title="Erik <ekoleszar@gmail.com>"> Erik</a> <pre>I had the same issue while connecting a second monitor, with the following card: VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660G] (prog-if 00 [VGA controller]) The problem arised when I updated to kernel 4.0.1-1-ARCH #1 SMP PREEMPT (updated some other packets also, like mesa 10.5.4-1). It worked after the RADEON_VA=0 fix described at the beggining, but in dmesg still appears <a href="attachment.cgi?id=115642" name="attach_115642" title="dmesg still with errors">attachment 115642</a> <a href="attachment.cgi?id=115642&action=edit" title="dmesg still with errors">[details]</a>: [ 57.343370] [drm:atom_op_jump [radeon]] *ERROR* atombios stuck in loop for more than 5secs aborting [ 57.343388] [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing 3336 (len 2642, WS 0, PS 8) @ 0x393E [ 62.462796] [drm:atom_op_jump [radeon]] *ERROR* atombios stuck in loop for more than 5secs aborting [ 62.462815] [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing 3336 (len 2642, WS 0, PS 8) @ 0x393E [ 62.547688] [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery reached max voltage [ 62.547715] [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>