Clock problem

David Schleef ds at
Tue Jul 31 12:04:26 EST 2001

On Mon, Jul 30, 2001 at 06:16:32PM +0200, Martin Costabel wrote:
> Bastien Nocera wrote:
> > mean ? not really, goes back to 1933 after each reboot...
> You don't mean 1903? 'Cause that's what I get (December 31, 1903) after
> each try to boot either 2.4.7-ben0 or 2.4.8-pre1( on my
> iBook1-FW. 2.4.7-ben0 goes up to ..mounting local file systems.. and
> then dumps me into xmon from a process ksoftirqd_CPU0 or something
> similar. At leaving xmon, it shuts down hard, the PRAM is zapped, and it
> is Dec 31, 1903. This is worse than taking out the battery, which gives
> Jan 1st, 1904.

1933 is significant because it is 2^31 seconds in the past.
Apparently, there is a difference in the way that stime() and
settimeofday() operate, since the date command works correctly
when the year is set to 1903 (and uses stime()), whereas ntpdate
does not.  (ntpdate uses settimeofday()).  Then again, it might
just be a bug in ntpdate.


** Sent via the linuxppc-dev mail list. See

More information about the Linuxppc-dev mailing list