From owner-freebsd-stable@FreeBSD.ORG Mon Dec 3 02:48:13 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 23B7E16A420 for ; Mon, 3 Dec 2007 02:48:13 +0000 (UTC) (envelope-from tundra@tundraware.com) Received: from ozzie.tundraware.com (ozzie.tundraware.com [75.145.138.73]) by mx1.freebsd.org (Postfix) with ESMTP id E203313C467 for ; Mon, 3 Dec 2007 02:48:12 +0000 (UTC) (envelope-from tundra@tundraware.com) Received: from [192.168.0.2] (viper.tundraware.com [192.168.0.2]) (authenticated bits=0) by ozzie.tundraware.com (8.14.2/8.14.2) with ESMTP id lB32bv2q041388 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO) for ; Sun, 2 Dec 2007 20:37:58 -0600 (CST) (envelope-from tundra@tundraware.com) Message-ID: <47536C03.50200@tundraware.com> Date: Sun, 02 Dec 2007 20:37:55 -0600 From: Tim Daneliuk Organization: TundraWare Inc. User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <200712021502.37344.doconnor@gsoft.com.au> <2a41acea0712021734l32e73d64jd34272a23e487c8@mail.gmail.com> In-Reply-To: <2a41acea0712021734l32e73d64jd34272a23e487c8@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-tundraware.com-MailScanner-Information: Please contact the ISP for more information X-tundraware.com-MailScanner: Found to be clean X-tundraware.com-MailScanner-From: tundra@tundraware.com X-Spam-Status: No Subject: Re: Intel S3000AH stall on boot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: tundra@tundraware.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Dec 2007 02:48:13 -0000 Jack Vogel wrote: > On Dec 1, 2007 8:32 PM, Daniel O'Connor wrote: >> Hi, >> I am doing some work for a company that recently bought 2 systems based >> on the above motherboard and mostly they work fine, however on boot >> just before userland starts they stall for about a minute. (Just after >> it starts the second CPU). > > Did you happen to check if during that time the floppy disk is being accessed? > If it is just reconfig the kernel with that device out and the hang > won't happen. > > That is the only hang that I've seen that lasts that long. > > Jack Or you can just turn it off in the BIOS to avoid having to fiddle with the kernel. *Why* this is happening is of more interest to me. ISTM that the kernel startup logic should be able to detect a floppy drive with no disk in it and move on promptly. I believe this because that is exactly what 4.x did ... well, now that I think about it, I never tried 4.x on the Intel MOBO that is causing this aggravation here.... ---------------------------------------------------------------------------- Tim Daneliuk tundra@tundraware.com PGP Key: http://www.tundraware.com/PGP/