Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 03 Dec 2000 20:23:03 +0100
From:      "Roger 'Rocky' Vetterberg" <rocky@ljusdal.net>
To:        gracchus@inficad.com, freebsd-questions@freebsd.org
Subject:   RE: FBSD 4.1: First Install: microuptime()???
Message-ID:  <3A2A9D97.51CE35D3@ljusdal.net>

next in thread | raw e-mail | index | archive | help

--------------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

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Tom snell wrote:
<p><i>>Well, I took the BSD plunge after 4 years of Linux, and it isn't</i>
<br><i>>pretty.&nbsp; The install itself went OK (from the 4.1 CD's in
the BSD</i>
<br><i>>Desktop Edition), but on boot I get a rapidly, then slower, repeating</i>
<br><i>>line, with incrementing values:</i>
<br><i>></i>
<br><i>>microuptime() went backwards (437.201814 -> 437, -694864070)</i>
<br>&nbsp;
<p>I have seen this happen several times, thou I have never experienced
it myself.
<br>The only thing the boxes have had in common, is that they have all
been AMD's.
<br>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.
<br>I hate to believe it, but could it be that FreeBSD has a problem with
certain AMD's?
<br>&nbsp;
<br>&nbsp;</html>

--------------6AB587D91E3B9AEDEAC16798--



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?3A2A9D97.51CE35D3>