Re: macppc time weirdness?

[Dale Rahn <drahn@dalerahn.com>]

Yes, macppc has a messed up clock in -current.
A prelimiary timer diff is currently being tested it will likely 
go into the tree in the next couple of days.

In the meantime macppc/macppc/clock.c can be reverted to 1.11

On Fri, Jan 02, 2004 at 11:36:22AM -0600, joshua stein wrote:
> can anyone else reproduce this on a -current macppc (or other
> architectures):
> 
> jcs@vorsicht:~> date; sudo rdate -n ntp.dls.net; date
> Fri Jan  2 11:51:28 CST 2004
> Fri Jan  2 11:30:54 CST 2004
> Fri Jan  2 11:51:28 CST 2004
> 
> jcs@vorsicht:~> rdate -np ntp.dls.net
> Fri Jan  2 11:32:23 CST 2004
> jcs@vorsicht:~> sudo date 1132
> Fri Jan  2 11:32:00 CST 2004
> Exit 2
> jcs@vorsicht:~> date
> Fri Jan  2 11:52:35 CST 2004
> 
> now if i try to set it far back it will go, but is still not
> accurate:
> 
> jcs@vorsicht:~> date
> Fri Jan  2 11:53:06 CST 2004
> jcs@vorsicht:~> sudo date 1100
> Fri Jan  2 11:00:00 CST 2004
> Exit 2
> jcs@vorsicht:~> date
> Fri Jan  2 11:20:35 CST 2004
> 
> kern.securelevel is at 1.  this is on a powerbook g4 with a -current
> kernel.  i have rdate trying to set the time at boot (rdate_flags
> set to "-n ntp.dls.net") but it never sets the time correctly (or
> gives any indication of a failure).
> 

Dale Rahn				drahn@dalerahn.com