Description of problem: many times the Xorg session crash after disconnect the HDMI cable and suspend the computer... this give me a Xorg session crash... Version-Release number of selected component (if applicable): [maximi89@localhost /]$ uname -a Linux localhost.localdomain 2.6.37-2.fc15.x86_64 #1 SMP Fri Jan 7 14:57:36 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux How reproducible: seems to happen always Steps to Reproduce: 1.connect and HDMI cable 2.disconnect the cable 3.try to suspend the computer Actual results: Xorg crash Expected results: to suspend without problems... Additional info: i'm running some packages of Xorg of rawhide, and the rest are F14 one, i'm running compiz in replace of metacity.
Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue. Please add drm.debug=0x04 to the kernel command line, restart computer, and attach * your X server config file (/etc/X11/xorg.conf, if available), * X server log file (/var/log/Xorg.*.log) * output of the dmesg command, and * system log (/var/log/messages) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above. We will review this issue again once you've had a chance to attach this information. Thanks in advance.
i have updated to kernel 2.6.38 [maximi89@localhost /]$ uname -r 2.6.38-0.rc3.git0.1.fc15.x86_64 now it suspend, but when i try to resume happens two things, one, it resume but it show some rare problems with the disk and can't load i8042 driver, so no touchpad and no keyboard... but Xorg working fine... another problem it show the same but can't load the Xorg.... So, that are the news... i will try what you said.
Created attachment 477882 [details] xorg.conf
Created attachment 477883 [details] xorg.0.log
Created attachment 477884 [details] xorg.1.log
Created attachment 477885 [details] dmesg
Created attachment 477886 [details] /var/log/messages
I don't understand your issue, please restrict this bug to GPU/Graphic related issue, open other bug for the other issues. If Xorg is working after resume than close this bug, if it's not working explain how it fails
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 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 this bug is closed as described in the policy above. 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.