From owner-freebsd-stable Sat Apr 13 9: 0:50 2002 Delivered-To: freebsd-stable@freebsd.org Received: from ns2.robhughes.com (12-237-138-77.client.attbi.com [12.237.138.77]) by hub.freebsd.org (Postfix) with SMTP id BF19F37B400 for ; Sat, 13 Apr 2002 09:00:44 -0700 (PDT) Received: (qmail 332 invoked from network); 13 Apr 2002 16:00:44 -0000 Received: from hexch01.robhughes.com (192.168.1.3) by ns2.robhughes.com with SMTP; 13 Apr 2002 16:00:44 -0000 Received: from kahuna-ws.robhughes.com ([192.168.1.16]) by HEXCH01.robhughes.com with Microsoft SMTPSVC(5.0.2195.4905); Sat, 13 Apr 2002 11:00:43 -0500 Subject: Re: System time issue in Asus P2B-F From: Rob Hughes To: freebsd-stable@freebsd.org In-Reply-To: <20020413125700.341C837B404@hub.freebsd.org> References: <20020413125700.341C837B404@hub.freebsd.org> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.3 (1.0.3-3) Date: 13 Apr 2002 11:01:17 -0500 Message-Id: <1018713677.5258.7.camel@kahuna-ws.robhughes.com> Mime-Version: 1.0 X-OriginalArrivalTime: 13 Apr 2002 16:00:43.0838 (UTC) FILETIME=[5DEEA5E0:01C1E304] Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 2002-04-13 at 07:57, Johann Frisch wrote: > On 10 Apr 2002, you wrote: > > > I've run into a very strange issue on one of my boxes. The > > system is a P2 333 on an Asus P2B-F running 4.5-STABLE and > > cvsup'ed as of yesterday, though the problem has been > > occurring for awhile now. What happens is that the system time > > is incrementing at about double the real world rate. Booting > > the system to the BIOS screen and using a stopwatch, I've > > verified that the hardware clock is keeping accurate time, so > > I don't think its the on-board clock chip. I've tried > > recompiling the kernel with the various CLK_ options, neither > > of which seemed to help. I also tried removing the HZ option > > as well as changing it. What other option or device entries > > should I be looking at? I'm at a dead-end, but need to find a > > solution as this is my primary firewall/IDS system and this > > issue is really borking things up in the logs. I've also tried > > running ntpd, but still no help, as well as removing and > > recreating the /etc/timezone file. > > Did you try syctl kern.timecounter.method (0 or 1) and > kern.timecounter.hardware (i8254 or TSC)? I had this racing system > time problem some time ago under FreeBSD 4.3 and it went away when > I changed kern.timecounter.hardware from TSC to i8254. > -- No go... If I compile with any CLK or HZ option, the system time goes ballistic. If I leave them out. I get kern.timecounter.method: 0 kern.timecounter.hardware: i8254 Setting these same options via sysctl.conf doesn't help, nor does changing them. I really think this is a code issue in -STABLE, but may be wrong. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message