Bug 53462 - clock wrong after suspend
Summary: clock wrong after suspend
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: apmd
Version: 7.1
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Aaron Brown
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-09-09 21:44 UTC by Scott Otterson
Modified: 2014-03-17 02:23 UTC (History)
1 user (show)

(edit)
Clone Of:
(edit)
Last Closed: 2005-02-02 22:47:18 UTC


Attachments (Terms of Use)

Description Scott Otterson 2001-09-09 21:44:57 UTC
After returning from a system sleep on my laptop, the system time is
incorrect.  The problem occurred after I ran the program to upgrade RH6.2
to 7.1.  In 6.2, the clock was correct after suspend

Comment 1 Bernhard Rosenkraenzer 2001-09-11 09:27:59 UTC
Is the UTC={true,false} setting in /etc/sysconfig/clock correct?



Comment 2 Scott Otterson 2001-09-11 14:54:01 UTC
It's set to false.   But isn't true also a correct answer?

Comment 3 Scott Otterson 2001-09-11 15:45:20 UTC
I looked into this a bit more:  UTC is set to false. This seems to be correct,
because hwclock gives this answer: 

/sbin/hwclock  
Tue 11 Sep 2001 08:40:40 AM PDT  0.348267 seconds

In any case, the problem does not seem to be the hardware clock.  If I suspend
and then unsuspend, and then look and the hardware clock again, it is still
correct.  However, the date command shows that the system time is wrong.  For
example:

date -s 08:40
Tue Sep 11 08:40:00 PDT 2001

/sbin/hwclock  --systohc

/sbin/hwclock  
Tue 11 Sep 2001 08:40:40 AM PDT  0.348267 seconds

<suspend>
<unsuspend>

/sbin/hwclock  
Tue 11 Sep 2001 08:41:56 AM PDT  0.617520 seconds

date
Tue Sep 11 01:42:02 PDT 2001

Do you need me to run any other tests?

Comment 4 Bill Nottingham 2005-02-02 22:47:18 UTC
Closing out bugs on older unsupported releases. Apologies for any lack
of response. Please reopen if it persists on current releases such as
Fedora Core 3.


Note You need to log in before you can comment on or make changes to this bug.