Bug 205773
Summary: | Software suspend doesn't work | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Philip Ashmore <contact> |
Component: | pm-utils | Assignee: | Phil Knirsch <pknirsch> |
Status: | CLOSED WORKSFORME | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5 | CC: | austin, camilo, edgar.hoch, mcepl, ncunning, opensource, pjones, richard, rvokal, tmus, tomiii, w.j.murray |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-08-30 18:21:05 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: |
Description
Philip Ashmore
2006-09-08 13:26:57 UTC
Why am I on Cc for this bug? Me too? I'm the GNOME Power Manager maintainer. I don't run KDE and I don't even have a nvidia card. I cloned Bug 183709 to produce my bug report - I guess the CC's got cloned too. Sounds to me like a problem with hal/dbus. They should be doing a chvt before the echo disk > /sys/power/state (and back afterwards). We aready do this in pm-utils. Hmm. I thought you did. So then, what could be going wrong that it's not switching. Is there any way to disable the chvt, Richard? Best best is to grab pjones and ask him what the plans are for pm-utils. Have a look at the pm-utils source and you'll see what we are doing already. Have you tried this with newer version of pm-utils? There are quite a few changes in the FC6 version of it that might fix the problem you're describing. Thanks, Read ya, Phil Sorry I took so long to respond. I've stated the version of the kernel it works on. Obviously I would be using the software suspend kernel of the same version. I also stated the version it doesn't work on. One or more of the patches between these two versions is imho responsible for this problem. As well as these versions, you imho should be able to track the versions of the other packages that were distributed within the updates repository snapshot - I don't know how I could attempt this. There is also no way I could "roll forward" between update snapshots from the DVD repository to the updates repository snapshot containing the kernel version I mentioned, in order to determine exactly when this feature stopped working. Obviously I would need to invest in a much larger hard disk to store each and every update repo snapshot in order to do this, as well as client side intelligence to recognize that the updates repo I'm mirroring locally is a new snapshot, not an update/correction to an existing snapshot - an updates repo release number or time stamp in a simple text file accompanying the updates repo would solve this, Even if I had these snapshots available and could do this, we still have more issues. 1. Was the updates repo snapshot containing the kernel version I had problems with tested by anyone with the same make/model laptop as I've got? 2. Did the regression/release tests run on the updates repo snapshot cover this case? I'm not even sure how one could automatically test hibernation without either a) specialized test rigging to compare the video output and disk activity to that expected within margins. b) manual testing. Looking forward to your response Philip Ashmore (In reply to comment #10) > I also stated the version it doesn't work on. What's the kernel version it does work on? Are you using the nv driver? > One or more of the patches between these two versions is imho responsible for > this problem. As well as these versions, you imho should be able to track the > versions of the other packages that were distributed within the updates > repository snapshot - I don't know how I could attempt this. You can't. > Even if I had these snapshots available and could do this, we still have more > issues. > 1. Was the updates repo snapshot containing the kernel version I had problems > with tested by anyone with the same make/model laptop as I've got? I very much doubt it. > 2. Did the regression/release tests run on the updates repo snapshot cover this case? There are currently no regression tests for hibernate or suspend, but we are working on it for the long term future. > Looking forward to your response You need to install a stock F7, do all the updates, and then follow the instructions on http://people.freedesktop.org/~hughsient/quirk/ Richard. FC5 is now end of life, so sadly this bug won't be fixed in this release. Is this bug still present in FC6 or F7? Not in its original form - see "https://bugzilla.redhat.com/show_bug.cgi?id=250033". (In reply to comment #13) > Not in its original form - see "https://bugzilla.redhat.com/show_bug.cgi?id=250033". ok, I close this bug then. |