http://qa.mandrakesoft.com/show_bug.cgi?id=3125





------- Additional Comments From [EMAIL PROTECTED]  2003-03-11 06:52 -------
I saw something very much like this in Mandrake 9.0.  I had trouble with the 
clock being left at GMT after a resume on a desktop computer.  I had left the 
apmd service off.  Running "service apmd start" partially solved the problem 
since one needs to have the apmd service started to run the power management 
scripts. 
 
The clock resetting, however was delayed for a minute or so after resumming.  
Further investigation revealed that /etc/sysconfig/apmd had the net and nfs 
parameters set to yes causing a considerable delay in completing 
/etc/sysconfig/apm-scripts/resume.d/4network because I was off of a network.  
As a result, the clock would not be set quickly as 7clock is run near the end 
of the resume.d scripts. 
 
Also, there is an error in the /etc/sysconfig/apm-scripts/apmd-proxy script 
where a "suspend,system" should be "suspend system".  This error didn't cause 
any problem because the parameter "on_ac_power" was not set. (Should it have 
been?) 
 



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.



------- Reminder: -------
assigned_to: [EMAIL PROTECTED]
status: NEW
creation_date: 
description: 
When waking up my laptop from suspend, the clock jumps to GMT. However, the
timezone is still set to the correct zone (that is, it hasn't moved to GMT, only
the time has). "hwclock" returns the correct time and time zone.

Example: date = 18:00 CET -> suspend for ten minutes -> date = 19:10 CET.

This is on a ThinkPad 390X.

(Also, I'm not sure if kernel is te right spot for this, but I figured it was
worth a shot.)

Reply via email to