From owner-freebsd-current@FreeBSD.ORG Fri Nov 19 18:21:09 2010 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from [127.0.0.1] (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id 697D11065670; Fri, 19 Nov 2010 18:21:08 +0000 (UTC) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-current@FreeBSD.org Date: Fri, 19 Nov 2010 13:20:53 -0500 User-Agent: KMail/1.6.2 References: <4CE6ACEF.4000303@freebsd.org> In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Message-Id: <201011191320.59156.jkim@FreeBSD.org> Cc: Ivan Voras , Andriy Gapon , Garrett Cooper Subject: Re: A big-ish machine, cannot boot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2010 18:21:09 -0000 On Friday 19 November 2010 12:04 pm, Garrett Cooper wrote: > On Fri, Nov 19, 2010 at 8:59 AM, Andriy Gapon wrote: > > on 19/11/2010 18:57 Ivan Voras said the following: > >> On 19 November 2010 17:13, Gary Jennejohn wrote: > >>> On Fri, 19 Nov 2010 17:51:22 +0200 > >>> > >>> Andriy Gapon wrote: > >>>> on 19/11/2010 17:41 Ivan Voras said the following: > >>>>> Fujitsu TX300 > >>>> > >>>> [Thunderbird 3 sometimes fails quoting while replying - blame > >>>> it] > >>>> > >>>> Perhaps I am wrong, but isn't the "twirly" shown by the > >>>> loader, still? Not sure if the kernel does that. > >>> > >>> Yup, that's the boot loader.  The kernel spits out printfs. > >> > >> Good news, of sorts - I left while I went for dinner and > >> apparently it did boot in the meantime. So it's not a complete > >> hang, it just takes unexpectedly long (10+ minutes?) > >> > >> I'm currently running "make -j24 buildworld" and once it boots > >> it looks very fast! > > > > You ought to determine a cause of the long boot, though. > > No compromises or excuses! :-) > > A similar issue occurred with an HP box recently (in the last 3-4 > months?). I'd check the archives for more details. I bet these are "legacy free" machines, right? I recently noticed that recent Intel chipsets cause incredibly long delays when non-existent ISA ports are accessed, most notably AT keyboard ports. (My gut tells me it is going in and out of SMM repeatedly for nothing.) Back in the old days, when we had real ISA bus, it used to delay very short and fixed amount time. Those days, this behaviour was even (ab)used as a delay function where a real timer is not available yet. ;-) Try getting rid of all unnecessary device drivers from your kernel configuration. Jung-uk Kim