From owner-freebsd-questions Sat Dec 2 23:25:47 2000 Delivered-To: freebsd-questions@freebsd.org Received: from sunny.pacific.net.sg (sunny.pacific.net.sg [203.120.90.127]) by hub.freebsd.org (Postfix) with ESMTP id 462BF37B400 for ; Sat, 2 Dec 2000 23:25:42 -0800 (PST) Received: from pop1.pacific.net.sg (pop1.pacific.net.sg [203.120.90.85]) by sunny.pacific.net.sg with ESMTP id eB37P1o23233; Sun, 3 Dec 2000 15:25:07 +0800 (SGT) Received: from gchang (spoff250.pacific.net.sg [203.120.94.250]) by pop1.pacific.net.sg with SMTP id PAA07643; Sun, 3 Dec 2000 15:24:48 +0800 (SGT) Message-ID: <016e01c05cf9$cdde8ba0$fa5e78cb@gchang> From: "James Lim" To: , , , References: <3A2A9D97.51CE35D3@ljusdal.net> Subject: Re: FBSD 4.1: First Install: microuptime()??? Date: Sun, 3 Dec 2000 15:22:20 +0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_016B_01C05D3C.D44FE2C0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_016B_01C05D3C.D44FE2C0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi there, Upon checking the mailing lists..it seems to has to do with = some APM management with some amd mobos. I might be wrong. But so far i = haven't got that error on my amd chip yet. Can anyone verify exactly = where this error would come from? I have a friend using intel on a = notebook and he is having the same problem. So could it be AMD? or just = certain motherboards/hardisks Regards, James Lim ----- Original Message -----=20 From: Roger 'Rocky' Vetterberg=20 To: gracchus@inficad.com ; freebsd-questions@FreeBSD.ORG=20 Sent: Monday, December 04, 2000 3:23 AM Subject: RE: FBSD 4.1: First Install: microuptime()??? Tom snell wrote:=20 >Well, I took the BSD plunge after 4 years of Linux, and it isn't=20 >pretty. The install itself went OK (from the 4.1 CD's in the BSD=20 >Desktop Edition), but on boot I get a rapidly, then slower, repeating = >line, with incrementing values:=20 >=20 >microuptime() went backwards (437.201814 -> 437, -694864070)=20 =20 I have seen this happen several times, thou I have never experienced = it myself.=20 The only thing the boxes have had in common, is that they have all = been AMD's.=20 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.=20 I hate to believe it, but could it be that FreeBSD has a problem with = certain AMD's?=20 =20 =20 ------=_NextPart_000_016B_01C05D3C.D44FE2C0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi there,
 
       =20     Upon checking the mailing lists..it seems to has to = do with=20 some APM management with some amd mobos. I might be wrong. But so far i = haven't=20 got that error on my amd chip yet. Can anyone verify exactly where this = error=20 would come from? I have a friend using intel on a notebook and he is = having the=20 same problem. So could it be AMD? or just certain=20 motherboards/hardisks
 
Regards,
James Lim
 
----- Original Message -----
From:=20 Roger = 'Rocky'=20 Vetterberg
To: gracchus@inficad.com ; freebsd-questions@FreeBSD.O= RG=20
Sent: Monday, December 04, 2000 = 3:23=20 AM
Subject: RE: FBSD 4.1: First = Install:=20 microuptime()???

Tom snell wrote:=20

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

I have seen this happen several times, thou I have never = experienced it=20 myself.
The only thing the boxes have had in common, is that they = have all=20 been AMD's.
Twice, I have seen people take the harddrive out of = the AMD=20 machines and put it in a Intel based one, and the error have = disappered.
I=20 hate to believe it, but could it be that FreeBSD has a problem with = certain=20 AMD's?
 
 

------=_NextPart_000_016B_01C05D3C.D44FE2C0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message