From owner-freebsd-questions Wed Jan 30 8:58:56 2002 Delivered-To: freebsd-questions@freebsd.org Received: from web13304.mail.yahoo.com (web13304.mail.yahoo.com [216.136.175.40]) by hub.freebsd.org (Postfix) with SMTP id 79C5737B404 for ; Wed, 30 Jan 2002 08:58:47 -0800 (PST) Message-ID: <20020130165846.6147.qmail@web13304.mail.yahoo.com> Received: from [193.174.9.99] by web13304.mail.yahoo.com via HTTP; Wed, 30 Jan 2002 17:58:46 CET Date: Wed, 30 Jan 2002 17:58:46 +0100 (CET) From: =?iso-8859-1?q?m=20p?= Subject: Re: Microuptime() went backwards To: einbecker@gmx.net Cc: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit 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 Tobias Lange wrote: > > Hi! > > > Have you enable APM in your kernel? > > I am using a slightly modified GENERIC, and i haven't changed anything in > there. But, I found the following line in the kernel-config-file: > > device apm0 at nexus? disable flags 0x20 # Advanced Power > Management > > If I comment this line out, that should turn APM off, right? Yes, this is the line which enable/disables APM. Comment it out and build a new kernel. After that it should work. > > > In the past there was trouble with > > microuptime(), APM and one of the x86 architecture processors (IIRC AMD ... > > but not for sure). > > Hm - I AM using an AMD Athlon - so that might be the reason. Thanks a lot - > I'll see if it works. If you are searching for more information: in the mailinglist archives about half a year ago (for a maximum) was a comprehensive discussion about why and how this problem exists. Marc __________________________________________________________________ Gesendet von Yahoo! Mail - http://mail.yahoo.de Ihre E-Mail noch individueller? - http://domains.yahoo.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message