[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Shutdown causes time loss on a Toshiba Tecra 8000



> Linux uses a software clock, not the hardware clock, to keep track of
> time. Obviously, when the computer is suspended, that clock stops. The
> solution is to read the hardware time into the software clock (using
> hwclock --hctosys) on resume. Optionally, it can also store the time using
> --systohc on suspend. I had thought that debian did the first
> automatically; I never had problems with it. Check to make sure that APM
> is recieving suspend events before they happen, and has enough time to
> execute scripts. Do a "tail -f /var/log/daemon.log" before
> suspending/resuming, to see if it is. 

Here is the results of doing a "tail -f /var/log/daemon.log":

before suspend:

genoa:/home/bill# tail -f /var/log/daemon.log
Jan 19 08:04:46 localhost apmd[206]: Charge: -0.13%/min (0:08) 0:15 (98% 2:40)
Jan 19 08:05:03 localhost apmd[206]: Charge: -0.12%/min (0:08) 0:16 (98% 2:36)
Jan 19 08:05:20 localhost apmd[206]: Charge: -0.12%/min (0:08) 0:17 (98% 2:38)
Jan 19 08:05:36 localhost apmd[206]: Charge: -0.12%/min (0:09) 0:17 (98% 2:38)
Jan 19 08:05:53 localhost apmd[206]: Charge: -0.11%/min (0:09) 0:18 (98% 2:40)
Jan 19 08:06:10 localhost apmd[206]: Charge: -0.11%/min (0:09) 0:18 (98% 2:42)
Jan 19 08:06:26 localhost apmd[206]: Charge: -0.11%/min (0:09) 0:19 (98% 2:42)
Jan 19 08:06:43 localhost apmd[206]: Charge: -0.10%/min (0:10) 0:19 (98% 2:44)
Jan 19 08:07:00 localhost apmd[206]: Charge: -0.10%/min (0:10) 0:20 (98% 2:40)
Jan 19 08:07:16 localhost apmd[206]: On-line: * * * (100% 2:42)
                                                                      
after suspend:

Jan 19 10:01:22 localhost apmd[206]: Resume after 00:00:02 (100% 2:40)
Jan 19 10:01:50 localhost cardmgr[9359]: executing: './network suspend eth0'
Jan 19 10:01:50 localhost apmd[206]: pre_suspend: 'run-parts 
/etc/apm/suspend.d' returns 0
Jan 19 10:01:50 localhost cardmgr[9359]: executing: './serial suspend ttyS3'
Jan 19 10:02:02 localhost apmd[206]: Resume after 00:00:12 (100% unknown)
Jan 19 10:02:03 localhost apmd[206]: post_resume: 'run-parts 
/etc/apm/resume.d' returns 0
Jan 19 10:02:03 localhost cardmgr[9359]: executing: './network resume eth0'
Jan 19 10:02:03 localhost cardmgr[9359]: executing: './serial resume ttyS3'
Jan 19 10:02:04 localhost apmd[206]: Resume after 00:00:01 (100%
unknown)     

Does this all look okay?  Nothing jumps out at me as being wrong.

Cheers,

Mark.


_/~~~~~~~~\___/~~~~~~\____________________________________________________
____/~~\_____/~~\__/~~\__________________________Mark_Phillips____________
____/~~\_____/~~\________________________________mark@ist.flinders.edu.au_
____/~~\HE___/~~\__/~~\APTAIN_____________________________________________
____/~~\______/~~~~~~\____________________________________________________
__________________________________________________________________________
        "They told me I was gullible ... and I believed them!" 




Reply to: