Kip Macy km...@freebsd.org writes:
I will take a closer look. This is clearly a separate issue from the
loss of timer interrupts - I had assumed that they were related.
I've seen that you made some changes to the timer code. Is this related
to this issue?
Btw, VMWare didn't cut it either in
Can you please try with the latest sources and let me know if you
still see this?
Thanks,
Kip
On Mon, Feb 2, 2009 at 9:16 AM, Julian Stecklina j...@alien8.de wrote:
Mister Olli mister.o...@googlemail.com writes:
Hi,
I've had time problems too. The clock did not go backwards, but forwards
Mister Olli mister.o...@googlemail.com writes:
Hi,
I've had time problems too. The clock did not go backwards, but forwards
for some time sime, and then jumped back to a certain date. Like
Sun Jan 25 00:55:12 UTC 2009
...
Sun Jan 25 01:08:35 UTC 2009
Sun Jan 25 00:55:12 UTC 2009
Sun Jan
Hi,
Since I changed the sysctl wallclock, I don't have any time issues anymore.
make was mourning a lot about timestamps before, but this also has gone
now...
Best Kai
On 1/30/09 4:20 AM, Mister Olli mister.o...@googlemail.com wrote:
Hi,
I've had time problems too. The clock did not go
Mister Olli mister.o...@googlemail.com writes:
Hi,
I've had time problems too. The clock did not go backwards, but forwards
for some time sime, and then jumped back to a certain date. Like
Sun Jan 25 00:55:12 UTC 2009
...
Sun Jan 25 01:08:35 UTC 2009
Sun Jan 25 00:55:12 UTC 2009
Sun Jan
I have some fundamental stability bugs I'm trying to fix right now.
I'll fix that once these are addressed.
-Kip
On Thu, Jan 29, 2009 at 8:01 PM, Julian Stecklina j...@alien8.de wrote:
Mister Olli mister.o...@googlemail.com writes:
Hi,
I've had time problems too. The clock did not go
