Juan please disable CONFIG_APM_RTC_IS_GMT. Kernel does the right thing when it is disabled ALWAYS. When it is enabled it just confuses it.
Others who produce custom kernels may consider it as well :) > > Andrey, as you can expect, your theory was correct: it is indeed the GMT > setting in kernel: > > standard 2.4.22-0.6mdk kernel (CONFIG_APM_RTC_IS_GMT=y): > [EMAIL PROTECTED] jkeller]$ date > Mon Aug 18 17:39:56 CEST 2003 > (suspend, wake up) > [EMAIL PROTECTED] jkeller]$ date > Mon Aug 18 19:40:23 CEST 2003 > > modified kernel (# CONFIG_APM_RTC_IS_GMT is not set): > [EMAIL PROTECTED] jkeller]$ date > Mon Aug 18 17:47:05 CEST 2003 > (suspend, wake up) > [EMAIL PROTECTED] jkeller]$ date > Mon Aug 18 17:47:40 CEST 2003 > background. when APM_RTC_IS_GMT is disabled, kernel computes the difference between CMOS and kernel time immediately before going to sleep and restores kernel time taking difference in account after resuming. It works irrespectively of whether your system is using GMT or local time - for GMT diff will be (close to) zero, that's all. When APM_RTC_IS_GMT is enabled kernel does nothing taking kernel time be equal to CMOS time. This breaks for the case system is using local time producing observed time jumps. I am not sure about hwclock --hctosys (that is done in APM scripts); I have vague recollection that it did break in this case as well but I do not remember anymore why I came to this conclusion. Anyway APM_RTC_IS_GMT is redundant for RTC == GMT, is buggy for RTC == local so it should be killed. [...] > P.S. Andrey, I *think* I'm off your ISP's blacklist now. Knock on wood, this > will make it to you. > I got this just fine. Recently ISPs seem to go mad about blacklisting everything possible. Even more amusing is that whether my ISP is blacklisted or blacklists some address, they recommend contact the other server's admin in both cases :)
