From owner-freebsd-current Wed Aug 19 21:37:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA13277 for freebsd-current-outgoing; Wed, 19 Aug 1998 21:37:10 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA13264 for ; Wed, 19 Aug 1998 21:37:04 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id GAA02328; Thu, 20 Aug 1998 06:30:07 +0200 (CEST) To: Brian Somers cc: Mike Smith , current@FreeBSD.ORG Subject: Re: Unwanted sig24 problems? In-reply-to: Your message of "Wed, 19 Aug 1998 22:54:08 BST." <199808192154.WAA17907@awfulhak.org> Date: Thu, 20 Aug 1998 06:30:06 +0200 Message-ID: <2326.903587406@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199808192154.WAA17907@awfulhak.org>, Brian Somers writes: >The only way this can be happening AFAICT is if the value pointed at >by the global ``timecounter'' is fluctuating (going backwards).... It doesn't. >Does making ``struct timecounter *timecounter'' volatile in >kern_clock.c help ? I can't tell 'cos the machine that I got this >problem with was given back.... I doubt it, if you look at how it is used you will see why. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message