From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 67713] Freezes on Trinity 7500G Date: Fri, 08 May 2015 16:58:23 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1813545756==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id D64F66E97F for ; Fri, 8 May 2015 09:58:23 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1813545756== Content-Type: multipart/alternative; boundary="1431104303.Cad54d31.10444"; charset="UTF-8" --1431104303.Cad54d31.10444 Date: Fri, 8 May 2015 16:58:23 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=67713 --- Comment #9 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: [ 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. --1431104303.Cad54d31.10444 Date: Fri, 8 May 2015 16:58:23 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"

Comment # 9 on bug 67713 from 
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.
--1431104303.Cad54d31.10444-- --===============1813545756== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHA6Ly9saXN0 cy5mcmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9kcmktZGV2ZWwK --===============1813545756==--