From owner-freebsd-stable@FreeBSD.ORG Mon Dec 3 03:11:55 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 7DC7D16A41A for ; Mon, 3 Dec 2007 03:11:55 +0000 (UTC) (envelope-from fbsd-stable@mawer.org) Received: from outbound.icp-qv1-irony-out3.iinet.net.au (outbound.icp-qv1-irony-out3.iinet.net.au [203.59.1.148]) by mx1.freebsd.org (Postfix) with ESMTP id 11D4D13C467 for ; Mon, 3 Dec 2007 03:11:54 +0000 (UTC) (envelope-from fbsd-stable@mawer.org) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgAAAM4CU0fLzq3r/2dsb2JhbAAI X-IronPort-AV: E=Sophos;i="4.23,241,1194188400"; d="scan'208";a="189746455" Received: from unknown (HELO [10.24.1.1]) ([203.206.173.235]) by outbound.icp-qv1-irony-out3.iinet.net.au with ESMTP; 03 Dec 2007 12:11:53 +0900 Message-ID: <4753738F.3010208@mawer.org> Date: Mon, 03 Dec 2007 14:10:07 +1100 From: Antony Mawer User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: tundra@tundraware.com References: <200712021502.37344.doconnor@gsoft.com.au> <2a41acea0712021734l32e73d64jd34272a23e487c8@mail.gmail.com> <47536C03.50200@tundraware.com> In-Reply-To: <47536C03.50200@tundraware.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: Intel S3000AH stall 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: Mon, 03 Dec 2007 03:11:55 -0000 On 3/12/2007 1:37 PM, Tim Daneliuk wrote: > 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.... Another "me too". We saw this and wound up removing the floppy drive from the systems in order to avoid this lengthy delay on boot - we weren't using them anyway and it saved a whole $5 or so on the hardware costs... ;-) I seem to recall it was not purely a 6.x thing - as I'm sure that we have plenty of 6.x machines with FDDs that don't exhibit this hang - but it was only newer Intel motherboards (I think 9xx series onwards) that we were seeing the issue on... --Antony