From owner-freebsd-questions Fri Feb 22 10:33:20 2002 Delivered-To: freebsd-questions@freebsd.org Received: from vcnet.com (mail.vcnet.com [209.239.239.15]) by hub.freebsd.org (Postfix) with SMTP id 6597F37B404 for ; Fri, 22 Feb 2002 10:33:15 -0800 (PST) Received: (qmail 80204 invoked by uid 1001); 22 Feb 2002 18:33:10 -0000 Date: Fri, 22 Feb 2002 10:33:10 -0800 From: Jon Rust To: questions@freebsd.org Subject: microuptime() backwards deal Message-ID: <20020222103310.A20732@mail.vcnet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Operating-System: http://www.freebsd.org/ Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm running 4.4-Stable on an ABIT KA7 VIA KX133 and getting the dreaded microuptime() backwards problem. The clock suddenly sprints forward by huge leaps and bounds, and even ntpd cannot keep up. Searching through archives of postings, I see Greg Lehey mention turning off apm, or if that can't be done, throwing in a special kernel config. I've done both, but the problem remains. I see this at boot time: apm0: on motherboard apm: found APM BIOS v1.2, connected at v1.2 I have apm turned off in the BIOS, and I have this line in my kernel config: device apm0 at nexus? flags 0x31 However, the clock still goes whacko every few months, requiring a reboot to restore functionality to the machine. I'd rather not go through the struggles of replacing the mobo, but if that's my only option... Any other ideas? I don't see any mention of it in the release notes for 4.5. Thanks, jon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message