Comment # 9
on bug 67713
from Erik
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 attachment 115642 [details]:
[ 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
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
