From owner-freebsd-questions Sat Dec 2 23:22: 2 2000 Delivered-To: freebsd-questions@freebsd.org Received: from anakin.ljusdal.se (unknown [195.100.114.236]) by hub.freebsd.org (Postfix) with ESMTP id BCE6A37B400 for ; Sat, 2 Dec 2000 23:21:58 -0800 (PST) Received: from ljusdal.net (rocky.ljusdal.net [194.17.208.94]) (authenticated) by anakin.ljusdal.se (8.11.1/8.11.1) with ESMTP id eB37LlX02467; Sun, 3 Dec 2000 08:21:48 +0100 (CET) (envelope-from rocky@ljusdal.net) Message-ID: <3A2A9D97.51CE35D3@ljusdal.net> Date: Sun, 03 Dec 2000 20:23:03 +0100 From: "Roger 'Rocky' Vetterberg" Reply-To: rocky@ljusdal.net X-Mailer: Mozilla 4.72 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: gracchus@inficad.com, freebsd-questions@freebsd.org Subject: RE: FBSD 4.1: First Install: microuptime()??? Content-Type: multipart/alternative; boundary="------------6AB587D91E3B9AEDEAC16798" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --------------6AB587D91E3B9AEDEAC16798 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Tom snell wrote: >Well, I took the BSD plunge after 4 years of Linux, and it isn't >pretty. The install itself went OK (from the 4.1 CD's in the BSD >Desktop Edition), but on boot I get a rapidly, then slower, repeating >line, with incrementing values: > >microuptime() went backwards (437.201814 -> 437, -694864070) I have seen this happen several times, thou I have never experienced it myself. The only thing the boxes have had in common, is that they have all been AMD's. Twice, I have seen people take the harddrive out of the AMD machines and put it in a Intel based one, and the error have disappered. I hate to believe it, but could it be that FreeBSD has a problem with certain AMD's? --------------6AB587D91E3B9AEDEAC16798 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Tom snell wrote:

>Well, I took the BSD plunge after 4 years of Linux, and it isn't
>pretty.  The install itself went OK (from the 4.1 CD's in the BSD
>Desktop Edition), but on boot I get a rapidly, then slower, repeating
>line, with incrementing values:
>
>microuptime() went backwards (437.201814 -> 437, -694864070)
 

I have seen this happen several times, thou I have never experienced it myself.
The only thing the boxes have had in common, is that they have all been AMD's.
Twice, I have seen people take the harddrive out of the AMD machines and put it in a Intel based one, and the error have disappered.
I hate to believe it, but could it be that FreeBSD has a problem with certain AMD's?
 
  --------------6AB587D91E3B9AEDEAC16798-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message