From owner-freebsd-stable@FreeBSD.ORG Sat Jun 3 00:48:40 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 73C8E16A420 for ; Sat, 3 Jun 2006 00:48:40 +0000 (UTC) (envelope-from fbsd-stable@mawer.org) Received: from mail24.syd.optusnet.com.au (mail24.syd.optusnet.com.au [211.29.133.165]) by mx1.FreeBSD.org (Postfix) with ESMTP id DABE143D45 for ; Sat, 3 Jun 2006 00:48:39 +0000 (GMT) (envelope-from fbsd-stable@mawer.org) Received: from [127.0.0.1] (c220-237-120-88.thorn1.nsw.optusnet.com.au [220.237.120.88]) by mail24.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k530maqW006488; Sat, 3 Jun 2006 10:48:38 +1000 Message-ID: <4480DC6B.10306@mawer.org> Date: Sat, 03 Jun 2006 10:48:43 +1000 From: Antony Mawer User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: Jack Vogel References: <2a41acea0606011530wf7bca5du23711fbfbfbc81@mail.gmail.com> <1149241101.60897.58.camel@buffy.york.ac.uk> <2a41acea0606020943j1843d949kf8d25e3164255e43@mail.gmail.com> In-Reply-To: <2a41acea0606020943j1843d949kf8d25e3164255e43@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: 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: Sat, 03 Jun 2006 00:48:41 -0000 On 3/06/2006 2:43 AM, Jack Vogel wrote: > On 6/2/06, Gavin Atkinson wrote: >> On Thu, 2006-06-01 at 15:30 -0700, Jack Vogel wrote: >> > 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. >> >> Can you put a verbose dmesg up with debug.fdc.debugflags=255 set from >> the loader? >> >> I suspect you'll find it's floppy-related. Try setting >> hint.fdc.0.disabled="1" from the loader and seeing if it goes away. > > YUP, I hadnt looked before, but during the whole timeout the floppy > access light is on. There were some messages during boot from the > controller as well. I've seen this on a number of 6.0 production systems with exactly the same symptoms. Disabling the floppy controller removes the long delay. I've skimmed the change log for the fdc driver: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/fdc/ ... but there have been a huge number of commits over the recent few years. Any number of those sounds like potential candidates for introducing the problem, but it will need someone with a large degree of patience to try and identify where the problem started occurring. I might add that it seems very hardware dependent: unfortunately none of my test machines on-hand exhibit the problem or I might be able to do some testing myself... -Antony