From owner-freebsd-questions@FreeBSD.ORG Tue Nov 16 15:07:52 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0FCBD16A4CE for ; Tue, 16 Nov 2004 15:07:52 +0000 (GMT) Received: from limicola.its.uu.se (limicola.its.UU.SE [130.238.7.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id BC7EE43D2F for ; Tue, 16 Nov 2004 15:07:50 +0000 (GMT) (envelope-from ante@Update.UU.SE) Received: by limicola.its.uu.se (Postfix, from userid 205) id 250D24995; Tue, 16 Nov 2004 16:07:48 +0100 (MEZ) Received: from limicola.its.uu.se(127.0.0.1) by limicola.its.uu.se via virus-scan id s3039; Tue, 16 Nov 04 16:07:46 +0100 Received: from Psilocybe.Update.UU.SE (Psilocybe.Update.UU.SE [130.238.19.25]) by limicola.its.uu.se (Postfix) with ESMTP id B883B49B3 for ; Tue, 16 Nov 2004 16:07:45 +0100 (MEZ) Received: by Psilocybe.Update.UU.SE (Postfix, from userid 30086) id A437438012; Tue, 16 Nov 2004 16:07:45 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by Psilocybe.Update.UU.SE (Postfix) with ESMTP id A30E65C002 for ; Tue, 16 Nov 2004 16:07:45 +0100 (CET) Date: Tue, 16 Nov 2004 16:07:45 +0100 (CET) From: Andreas Davour To: freebsd-questions@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Mysterious freeze while booting X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Nov 2004 15:07:52 -0000 I have this odd behaviour from both my 5.2 and my 5.3 installations. GENERIC or my own. When booting the console displays the usual messages like below: 1> Starting local daemons:. 2> Updating motd. 3> Configuring syscons: keymap blanktime. 4> Initial i386 initialization:. 5> Additional ABI support: linux. 6> Starting cron. What is strange is that after line 3 the computer suddenly stops for a long time, almost a minute, doing (as far as I know) nothing! Then the following lines 4,5,6 flow forth and the systems boot like it should. I have examined the Handbook, and I have checked the scripts that produce this output and I don't understand what's happening. I also tried to run the process step-by-step by hand from single-user mode and it never showed that odd "sleep" period. Anyone have a clue? /Andreas -- George W. Bush won, so now the world will endure four more years of idiocy, arrogance and unwarranted bloodshed. Congratulation USA! I'm happy I'm not a part of it. My conscience is clean. Is yours?