From owner-freebsd-questions Tue Jun 11 21: 0:58 2002 Delivered-To: freebsd-questions@freebsd.org Received: from alpha.yumyumyum.org (dsl092-171-091.wdc1.dsl.speakeasy.net [66.92.171.91]) by hub.freebsd.org (Postfix) with ESMTP id 478B437B409 for ; Tue, 11 Jun 2002 21:00:52 -0700 (PDT) Received: from alpha.yumyumyum.org (localhost [127.0.0.1]) by alpha.yumyumyum.org (8.12.3/8.12.3) with ESMTP id g5C40P21018051; Wed, 12 Jun 2002 00:00:25 -0400 (EDT) (envelope-from culverk@yumyumyum.org) Received: from localhost (culverk@localhost) by alpha.yumyumyum.org (8.12.3/8.12.3/Submit) with ESMTP id g5C40O7N018048; Wed, 12 Jun 2002 00:00:24 -0400 (EDT) (envelope-from culverk@yumyumyum.org) X-Authentication-Warning: alpha.yumyumyum.org: culverk owned process doing -bs Date: Wed, 12 Jun 2002 00:00:24 -0400 (EDT) From: Kenneth Culver To: Brian Astill Cc: RJ45 , Subject: Re: Athlon and clock walking forward In-Reply-To: <200206120247.g5C2lk138461@tierzero.apana.org.au> Message-ID: <20020611235521.P18008-100000@alpha.yumyumyum.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 > Then perhaps you would tell the rest of us how you avoided this problem > which is so common for the rest of us? It is associated with a > "microuptime going backwards" error message repeated a dozen times per > second and the system clock going forward at an alarming rate. The only > way to stop this is . On reboot, time is OK, so the > hardware clock is not affected. > I ask again. How did you and your friends avoid this problem? > I didn't do anything different from any other FreeBSD install. I'd just say that FreeBSD might have problems with your specific motherboard or chipset, because I've had my athlon for a very long time (it's an 800Mhz Tbird) and I have at least 2 friends with newer model athlons (one with a 1.4GHz Tbird, and one with a Athlon XP 1700+) and they have not had problems either. None of us have done anything different from what we would've done with an intel system, and none of us have had problems. I know this doesn't help you much, but to me, even if your hardware works in windows, this is probably some issue that is specific to FreeBSD and your chipset/motherboard. Ken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message