From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 67713] Freezes on Trinity 7500G
Date: Fri, 08 May 2015 16:58:23 +0000 [thread overview]
Message-ID: <bug-67713-502-j4ziReS5ah@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-67713-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1256 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=67713
--- Comment #9 from Erik <ekoleszar@gmail.com> ---
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.
[-- Attachment #1.2: Type: text/html, Size: 2182 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-05-08 16:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-03 14:01 [Bug 67713] New: Atombios stuck in a loop on Trinity 7500G bugzilla-daemon
2013-08-03 14:11 ` [Bug 67713] " bugzilla-daemon
2013-08-03 14:14 ` bugzilla-daemon
2013-08-03 15:11 ` bugzilla-daemon
2013-08-03 15:18 ` bugzilla-daemon
2013-08-06 0:21 ` bugzilla-daemon
2013-08-06 0:22 ` bugzilla-daemon
2013-08-06 0:41 ` [Bug 67713] Freezes " bugzilla-daemon
2013-08-06 0:42 ` bugzilla-daemon
2015-05-08 16:56 ` bugzilla-daemon
2015-05-08 16:58 ` bugzilla-daemon [this message]
2015-09-11 13:51 ` bugzilla-daemon
2016-04-15 17:56 ` bugzilla-daemon
2016-10-12 16:11 ` bugzilla-daemon
2016-11-03 13:21 ` 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-67713-502-j4ziReS5ah@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).