Bug 825336
| Summary: | X can`t wake up monitor (APU HD 6550D) | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Martin Naď <martin.nad89> | ||||||||
| Component: | xorg-x11-drv-ati | Assignee: | X/OpenGL Maintenance List <xgl-maint> | ||||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 17 | CC: | franta, jforbes, jglisse, martin.marques, nlminhtl, samuel-rhbugs, xgl-maint | ||||||||
| Target Milestone: | --- | Keywords: | Reopened | ||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2013-08-01 18:13:03 UTC | Type: | Bug | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
Martin Naď
2012-05-25 18:01:12 UTC
Created attachment 586929 [details]
dmesg
Created attachment 586930 [details]
messages
Created attachment 586931 [details]
Xorg.0.log
I kill X server with ctrl+alt+Bckspc
Its must some change on output to wake up monitor (change resolution) *** This bug has been marked as a duplicate of bug 655039 *** Please dont mark bug as duplicate. Let us do that. A similar problem http://phoronix.com/forums/showthread.php?66117-AMD-A6-3500-mode-setting-issue-on-VGA-output upstream https://bugs.freedesktop.org/show_bug.cgi?id=42490 from dmesg: [drm:radeon_dp_link_train_cr] *ERROR* clock recovery reached max voltage [drm:radeon_dp_link_train_cr] *ERROR* clock recovery failed Maintainers, have you applied the patch
commit 700698e7c303f5095107c62a81872c2c3dad1702
Author: Alex Deucher <alexander.deucher>
Date: Fri Apr 27 17:18:59 2012 -0400
drm/radeon/kms: need to set up ss on DP bridges as well
In the 3.4.4-1 release?
Yes, this patch was in 3.4.0. According to the upstream bug, it did not fix the problem for several people. I stand here with this same problem. Computer goes to sleep and doesn't wake up the video driver. Computer is working as I can type and even reboot if I hit the right keys, That freedesktop bug doesn't seem to be the same issue as this one. It sounds to me like that one is about the monitor not turning on at all. This one is about it working for a while and then not working, maybe when the screen locks and turns off. I have an A8-3870 APU and kernel-3.5.2-1.fc17.x86_64. I was logged in and went away for a few minutes. When I came back the monitor was off and wouldn't turn back on. I checked the logs using ssh and found the messages mentioned above: [ 1363.859176] [drm:radeon_dp_link_train_cr] *ERROR* clock recovery reached max voltage [ 1363.859187] [drm:radeon_dp_link_train_cr] *ERROR* clock recovery failed with 3.5.5-2.fc17.i686.PAE kernel (from koji) now i'm working two days without this problem, thus it seem bug is solved (to 3.5.5 Fedora kernel was perhaps bacported some radeon patches from 3.6 kernel). Don't know when it got fixed because I was using the catalyst driver, but with 3.6.2, and with 3.6.6 it works like a charm. This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |