From owner-freebsd-stable@FreeBSD.ORG Thu Jun 1 22:30:52 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 534F916A4E5 for ; Thu, 1 Jun 2006 22:30:52 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from wx-out-0102.google.com (wx-out-0102.google.com [66.249.82.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id DEF9743D46 for ; Thu, 1 Jun 2006 22:30:51 +0000 (GMT) (envelope-from jfvogel@gmail.com) Received: by wx-out-0102.google.com with SMTP id i31so276751wxd for ; Thu, 01 Jun 2006 15:30:51 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=Mqeik/8YGM+FzN/wY1lnkcL+zYdtGRH+IhLALU8cwdYEs5U6QO8zzBafkdA8VtNruYjYSVakrkXGGKbmq6ZQ1jl2fHGBOoMdYaVihNEJ0EhU5t5uSmsaE+nNDUaXpJhocumiqgr2+qfRS5cUOxgbixtex6FICKJGBeZ96E6cpMc= Received: by 10.70.29.17 with SMTP id c17mr1422363wxc; Thu, 01 Jun 2006 15:30:51 -0700 (PDT) Received: by 10.70.77.18 with HTTP; Thu, 1 Jun 2006 15:30:51 -0700 (PDT) Message-ID: <2a41acea0606011530wf7bca5du23711fbfbfbc81@mail.gmail.com> Date: Thu, 1 Jun 2006 15:30:51 -0700 From: "Jack Vogel" To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: long timeout on boot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jun 2006 22:30:54 -0000 Both on my own machine, and on systems in our test group's lab, we notice these long (like 2min maybe?) delays near the end of boot. It seems to be ATA/SATA related. It has just announced the one disk it discovered, then shows the CPUs launched, and then it just sits printing nothing for, like I said, maybe a minute or two. Finally it will complete boot and all seems to be fine. I am guessing its in a detection loop maybe? Any ideas?? Oh, this is 6.1 RELEASE on i386, although I'm pretty sure x86_64 will show the same behavior. Jack