Bug 703927

Summary: Xorg broken suspend to ram
Product: [Fedora] Fedora Reporter: Martin Naď <martin.nad89>
Component: xorg-x11-drv-nouveauAssignee: Ben Skeggs <bskeggs>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 15CC: airlied, ajax, bskeggs, luigi.3010, mcepl
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-02-05 16:06:46 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
dmesg
none
pm-suspend.log
none
messages none

Description Martin Naď 2011-05-11 17:29:29 UTC
Description of problem:
suspend without running Xorg,work well.
suspend with running Xorg,everytime fail ,just show plymouth screen and hangs.

Version-Release number of selected component (if applicable):
kernel-2.6.38.5-22.fc15.i686
xorg-x11-server-common-1.10.1-14.fc15.i686
xorg-x11-server-utils-7.5-5.fc15.i686
xorg-x11-server-Xorg-1.10.1-14.fc15.i686
xorg-x11-drv-nouveau-0.0.16-24.20110324git8378443.fc15.i686

How reproducible:
everytime

Steps to Reproduce:
1.click to suspend (from *DE menu)
2.system try to suspend
3.hangs
  
Actual results:
suspend don`t work with running Xorg.

Expected results:
suspend work well

Additional info:

Comment 1 Martin Naď 2011-05-11 17:32:52 UTC
Created attachment 498353 [details]
dmesg

suspend without Xorg

Comment 2 Martin Naď 2011-05-11 17:35:08 UTC
Created attachment 498354 [details]
pm-suspend.log

Comment 3 Martin Naď 2011-05-11 17:41:11 UTC
Created attachment 498356 [details]
messages

Comment 4 Matěj Cepl 2011-05-14 19:30:40 UTC
Hi, Martin,

/var/log/Xorg.0.log would be probably useful. I know this is probably mostly KMS issue, but still, it could give us more context about what's going on.

And of course, I trust you, that you tried this without any /etc/X11/xorg.conf, right?

Thank you

Comment 5 Luigi Pardey 2011-12-31 15:40:02 UTC
Martin,

Could you provide the information you were asked for? If 30 days pass after this message without receiving the needed info we will have to close the bug due to inactivity

Thanks

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 6 Luigi Pardey 2012-02-05 16:06:46 UTC
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as INSUFFICIENT_DATA.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers