On Fri, Jul 16, 2010 at 11:47:23PM +0300, Alexander Motin wrote:
>
> It is probably hard to see pattern due to to very high clock frequency.
> But TSC timecounter is unreliable even on real SMP systems. What it
> counts on virtual SMP - even bigger question. As system seems never uses
> timecounte
On Fri, Jul 16, 2010 at 2:05 PM, Bruce Cran wrote:
> On Fri, Jul 16, 2010 at 11:47:23PM +0300, Alexander Motin wrote:
>>
>> It is probably hard to see pattern due to to very high clock frequency.
>> But TSC timecounter is unreliable even on real SMP systems. What it
>> counts on virtual SMP - even
Bruce Cran wrote:
> On Fri, Jul 16, 2010 at 11:47:23PM +0300, Alexander Motin wrote:
>> It is probably hard to see pattern due to to very high clock frequency.
>> But TSC timecounter is unreliable even on real SMP systems. What it
>> counts on virtual SMP - even bigger question. As system seems nev
Rob Farmer wrote:
>>> @@ -81,7 +81,10 @@
>>> ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode
>>> ppc0: [ITHREAD]
>>> ppbus0: on ppc0
>>> -atrtc0: at port 0x70 irq 8 on isa0
>>> +atrtc0: at port 0x70 irq 8 on isa0
>>> +atrtc0: [FILTER]
>>> +Event timer "RTC" frequency 32768 Hz quality 0
On Thu, Jul 15, 2010 at 11:33 PM, Alexander Motin wrote:
> Rob Farmer wrote:
>> I have a VPS from rootbsd.net which is running current, though I don't
>> update it very often. I just built and installed a new world and
>> kernel and now the clock will not move from the time the system was
>> boote
Rob Farmer wrote:
> I have a VPS from rootbsd.net which is running current, though I don't
> update it very often. I just built and installed a new world and
> kernel and now the clock will not move from the time the system was
> booted, ie:
> # date
> Thu Jul 15 16:15:58 PDT 2010
>
> # date
> Thu
