From owner-freebsd-questions Tue Aug 14 18:35:58 2001 Delivered-To: freebsd-questions@freebsd.org Received: from daemon.jointcs.net (206.suaa.wash.washdctt.dsl.att.net [12.98.96.206]) by hub.freebsd.org (Postfix) with ESMTP id 4E80837B40C for ; Tue, 14 Aug 2001 18:35:53 -0700 (PDT) (envelope-from ajoint@jointcs.net) Received: from localhost (ajoint@localhost) by daemon.jointcs.net (8.11.1/8.11.1) with ESMTP id f7F1ZiE00285; Tue, 14 Aug 2001 21:35:45 -0400 (EDT) (envelope-from ajoint@jointcs.net) Date: Tue, 14 Aug 2001 21:35:44 -0400 (EDT) From: Anthony Joint To: FreeBSD-Questions Cc: Irwan Hadi Subject: Re: What are these strange microuptime messages? Message-ID: 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 Irwan, Did you ever find an answer to your problem? I have a Duron 900 on an Abit KT7A and am having the same message when I run ftp (client) If I use ssh and scp the file it works just fine. I do not have apmd set to run at boot, however I am still using the GENERIC kernel. Original Message: I also got the same problem, on a freeBSD 4.3 release, on an AMD Athlon 1.2 Ghz, 640 M Memory (512 MB PC 133 CAS 3 Mushkin with Nanya Chips, and 128 M PC 133 CAS 2 Rev 2 Mushkin), and 40 GB Maxtor 7200 RPM. The motherboard is the newest Asus Ali Magik 1. On that computer I'm doing nothing, and the computer is still in burn test (although its already 20 days). I just turn on the computer after I installed freeBSD there, and leave it alone. Is it because memory problem, or because AMD, or what? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message