From owner-freebsd-current Wed Oct 30 2: 0:19 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 84C8A37B401 for ; Wed, 30 Oct 2002 02:00:18 -0800 (PST) Received: from flamingo.mail.pas.earthlink.net (flamingo.mail.pas.earthlink.net [207.217.120.232]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0D3B043E88 for ; Wed, 30 Oct 2002 02:00:18 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0004.cvx22-bradley.dialup.earthlink.net ([209.179.198.4] helo=mindspring.com) by flamingo.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 186pe0-0000da-00; Wed, 30 Oct 2002 02:00:12 -0800 Message-ID: <3DBFAD5F.3D7B31FC@mindspring.com> Date: Wed, 30 Oct 2002 01:58:55 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Stijn Hoop Cc: Garance A Drosihn , Raymond Kohler , current@freebsd.org Subject: Re: speed of -CURRENT [was: questions about the state of current] References: <2570443.1035916854787.JavaMail.wshttp@emss03g01.ems.lmco.com> <20021030091356.GC94770@pcwin002.win.tue.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Stijn Hoop wrote: > I am experiencing a really noticable slower startup time on my very recent > -CURRENT laptop for almost all programs. The problem seems to be in getting > info in the cache, because it disappears when I start the same program again. > > It is even noticable when doing a simple 'ls -l' in an uncached directory (ie > boot the laptop, cd tmp/test && ls -l), but larger things, like starting X, > take roughly two or three times as long as on -STABLE. [ ... ] > The systems hostname was changed between Aug & Oct, but it's the > same laptop, a P3-800 w/256MB memory. > > Thoughts? The first thing you should do is check without ACPI loaded; the biggest indicator will probably be the dmesg for the reported clock rate, vs. what is installed in the machine (i.e. ACPI will occasionally result in the machine being "power managed" down to a lower clock rate. Check the -current archives; this is normally the result of bad ACPI P-code in the BIOS, and updating the BIOS usually fixes it (or else you can patch it, if you can verify that this is the problem). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message