Date: Wed, 12 Jun 2002 00:00:24 -0400 (EDT) From: Kenneth Culver <culverk@yumyumyum.org> To: Brian Astill <bastill@sa.apana.org.au> Cc: RJ45 <rj45@slacknet.com>, <freebsd-questions@FreeBSD.ORG> Subject: Re: Athlon and clock walking forward Message-ID: <20020611235521.P18008-100000@alpha.yumyumyum.org> In-Reply-To: <200206120247.g5C2lk138461@tierzero.apana.org.au>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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 <ctrl><alt><delete>. 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020611235521.P18008-100000>