Here is some of yesterday's notice-level log from my tor (0.2.0.23-rc)
server:
Apr 04 05:34:37.285 [warn] Your system clock just jumped 133 seconds forward;
assuming established circuits no longer work.
Apr 04 05:43:23.629 [warn] Your system clock just jumped 140 seconds forward;
assuming
On Sat, Apr 5, 2008 at 1:47 PM, Scott Bennett [EMAIL PROTECTED] wrote:
... Here is some of yesterday's notice-level log from my tor (0.2.0.23-rc)
...
Those are all of the messages issued thus far, so 0.2.0.19-alpha has been
running with no problems for over 25 hours. I will continue
On Tue, Apr 01, 2008 at 04:58:22AM -0500, [EMAIL PROTECTED] wrote 4.5K bytes in
68 lines about:
: hellas # sysctl machdep.hyperthreading_allowed=0
: machdep.hyperthreading_allowed: 1 - 0
Just for a test, have you tried disabling HT in the bios? I'll setup a
fbsd-7-stable sytem with
On Wed, 2 Apr 2008 09:21:44 -0400 [EMAIL PROTECTED] wrote:
On Tue, Apr 01, 2008 at 04:58:22AM -0500, [EMAIL PROTECTED] wrote 4.5K bytes
in 68 lines about:
: hellas # sysctl machdep.hyperthreading_allowed=0
: machdep.hyperthreading_allowed: 1 - 0
Just for a test, have you tried
On Mon, 31 Mar 2008 22:49:05 -0700 Lucky Greeen [EMAIL PROTECTED]
wrote:
Scott Bennett wrote:
It appears that the clock jump problem does persist into 0.2.0.23-rc.
Here are the notice-level log messages since I started up the new version
this afternoon:
[remainder eldided]
Scott,
On Mon, 31 Mar 2008 22:49:05 -0700 Lucky Greeen [EMAIL PROTECTED]
wrote:
[much deleted --SB]
There is a very simple way for you to test if the time jumps you have
been seeing are caused by the TSCs between two CPU cores being out of
sync: simply temporarily disable SMP in your kernel.
It appears that the clock jump problem does persist into 0.2.0.23-rc.
Here are the notice-level log messages since I started up the new version
this afternoon:
Mar 31 15:18:56.468 [notice] Tor 0.2.0.23-rc (r14173) opening log file.
Mar 31 15:18:56.468 [warn] Can't log to stdout with
Scott Bennett wrote:
It appears that the clock jump problem does persist into 0.2.0.23-rc.
Here are the notice-level log messages since I started up the new version
this afternoon:
[remainder eldided]
Scott,
If you are using a dual-core or multiprocessor system, it is likely
that you
8 matches
Mail list logo