Bug 28234
Summary: | move hwclock to higher in resume script | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Matthew Miller <mattdm> |
Component: | apmd | Assignee: | Bernhard Rosenkraenzer <bero> |
Status: | CLOSED RAWHIDE | QA Contact: | Aaron Brown <abrown> |
Severity: | low | Docs Contact: | |
Priority: | medium | ||
Version: | 7.1 | ||
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: | 2002-01-24 22:51: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: | |
Embargoed: |
Description
Matthew Miller
2001-02-18 22:22:45 UTC
Your clock shouldn't jump if you rebuild your kernel without CONFIG_APM_RTC_IS_GMT. Ah, yes, thanks. However, I've had trouble getting the kernel to rebuild cleanly, and this isn't exactly a fast system (and it's currently the only one I've got to test on...). Hopefully I'll have better luck with RC1. It'd still be nice for the hwclock setting to be moved up, for cases where something is broken. Moved to the 2nd thing (2nd only to getting the hard disks back up even with inherently broken BIOSes) in 3.0.2-6. |