Bug 542379
| Summary: | Suspend to ram/disk both fails | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Riku Seppala <riku.seppala> | ||||||
| Component: | xorg-x11-drv-nouveau | Assignee: | Ben Skeggs <bskeggs> | ||||||
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | low | ||||||||
| Version: | 12 | CC: | airlied, ajax, bskeggs, mbreuer, tcpip4000 | ||||||
| Target Milestone: | --- | Keywords: | Reopened | ||||||
| Target Release: | --- | ||||||||
| Hardware: | All | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2010-07-18 22:25:20 UTC | Type: | --- | ||||||
| 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
Riku Seppala
2009-11-29 15:01:55 UTC
Hi, Can you try with desktop effects turned (compiz) turned off? -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Desktop effects was off by default. I enabled, had to set compositing type to Xrender. Suspend to ram worked once but it didn't wake up. Now it's same as before. Maybe something got messed when I had to force shutdown by pressing the power button. I'm using kde if it makes any difference. Thank you for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers *** This bug has been marked as a duplicate of bug 473542 *** My denoting this as duplicate seems to have been premature. Riku, If you could, please look at the following and let me know if your output/experiences matches these: https://bugzilla.redhat.com/show_bug.cgi?id=473542 https://bugzilla.redhat.com/show_bug.cgi?id=517480 https://bugzilla.redhat.com/show_bug.cgi?id=492740 https://bugzilla.redhat.com/show_bug.cgi?id=508571 https://bugzilla.redhat.com/show_bug.cgi?id=471711 https://bugzilla.redhat.com/show_bug.cgi?id=542317 -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Forgot to mark need info on prior comment. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers I can reproduce this in a HP Pavilion dv6448se with a Geforce 6150 Go (rev a2): 1. Select Shut down -> Suspend 2. Immediately the screen turns black and the Caps-Lock led blinks continously (system crashed). Software: Fedora 12 Kernel 2.6.31.6-166.fc12.x86_64 Gnome 2.28.0 xorg-x11-drv-nouveau 0.0.15 Another info: There is no compiz activated. Trying to get a trace about this issue. --- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Created attachment 378030 [details] dmesg for hp6448se This file was generated using this commands: sync; echo 1 > /sys/power/pm_trace; pm-suspend Then rebooting machine and copying the dmesg information. --- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers The bug looks like bug #508571 but cannot define it is the same source of problem as this one, due to the hardware differences. Better the maintainer decide that. --- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers F13 + yum update sleep -> The Fedora logo stays on the screen, seems like total freeze. (caps lock light does not respond) hibernate -> screen goes black, the back light stays on. I can see screen flashes once, (and I think back light went off at this time) and then total freeze. CPU fan runs normally the whole time. What behaviour do you see if you boot with "3" appended to your boot options, login and run "echo mem > /sys/power/state", then resume? Also, what about booting with "nomodeset 3" and doing the same? On resume in this configuration, you won't likely get your display back, but you should be able to trigger disk activity etc to confirm the system resumed. Booting with "3" login as root, run "echo mem > /sys/power/state", cursor blinks a second and then I just see the "_" on the top left corner and system is frozen. With "nomodeset 3" it succesfully suspends but, resume fails just like you said. The laptop is broken now (motherboard). So I no longer can use it. So close this bug? Thanks for letting us know, closing. |