Bug 137782
Summary: | How To Disable Hibernation on FC2 ! | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Dr YoZeN <root> |
Component: | kernel | Assignee: | Dave Jones <davej> |
Status: | CLOSED WORKSFORME | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 2 | CC: | pfrields |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-11-02 04:45:33 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
Dr YoZeN
2004-11-01 09:28:38 UTC
Sounds like a kernel/X/APM bios interaction. In general, with ACPI, if you don't explicitly request a suspend, one isn't going to happen. It may happen with APM, though - you can almost certainly tweak your bios options. I don't understand this report at all. Unless you are trying to suspend, the suspend code shouldn't be triggering. Can you be a little more specific about what exactly happens ? Thank you for your help, I got it fixed ! I disabled acpid|ampd with 'chkconfig'. But I had to restart the Server after doing that. So actually the procedure should be : 1) Disabling APMD|ACPID 2) Restart the Machine (Necessary Step) The Dragon |