From owner-freebsd-current@FreeBSD.ORG Mon Aug 18 08:21:42 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 44CE537B401 for ; Mon, 18 Aug 2003 08:21:41 -0700 (PDT) Received: from alpha.siliconlandmark.com (alpha.siliconlandmark.com [209.69.98.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id E7F9643F85 for ; Mon, 18 Aug 2003 08:21:40 -0700 (PDT) (envelope-from andy@siliconlandmark.com) Received: from alpha.siliconlandmark.com (localhost [127.0.0.1]) h7IFLbfN003273; Mon, 18 Aug 2003 11:21:37 -0400 (EDT) (envelope-from andy@siliconlandmark.com) Received: from localhost (andy@localhost)h7IFLbbI003270; Mon, 18 Aug 2003 11:21:37 -0400 (EDT) (envelope-from andy@siliconlandmark.com) X-Authentication-Warning: alpha.siliconlandmark.com: andy owned process doing -bs Date: Mon, 18 Aug 2003 11:21:37 -0400 (EDT) From: Andre Guibert de Bruet To: Kevin Oberman In-Reply-To: <20030818151636.A4F255D08@ptavv.es.net> Message-ID: <20030818111704.R320@alpha.siliconlandmark.com> References: <20030818151636.A4F255D08@ptavv.es.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: Re: Slow Boot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Mon, 18 Aug 2003 15:21:42 -0000 On Mon, 18 Aug 2003, Kevin Oberman wrote: > > Date: Mon, 18 Aug 2003 11:09:05 -0400 (EDT) > > From: Andre Guibert de Bruet > > > > On Mon, 18 Aug 2003, Kevin Oberman wrote: > > > > > > From: Bill Moran > > > > > > > > Matthew D. Fuller wrote: > > > > > On Sun, Aug 17, 2003 at 02:55:46PM -0400 I heard the voice of > > > > > Bill Moran, and lo! it spake thus: > > > > > > > > > >>My best guess is that the chipset responds slowly to probes, thus it > > > > >>takes a while to get the list of devices from it. However, I've never > > > > >>looked into it any more than that. > > > > > > > > > > I've always presumed it to be a question of timing out probes to the > > > > > drives; it only ever happens on IDE controllers with no devices attached > > > > > to 'em. I habitually just disable the controller channels that are empty > > > > > (or, in the case of my SCSI systems, just yank ATA support altogether). > > > > > > > > Could be. This machine is pretty bare-bones. Single ATA HDD and nothing > > > > on the secondary controller. I never really considered that, but it makes > > > > sense that probes on the secondary controller would take the full timeout > > > > value if there was nothing to respond. > > > > > > Nope. My system has disks on both ATA controllers with hard drives as > > > the master for each channel. One channel also has the CD drive as > > > the slave. > > > > Does the hard drive that's on it's own have a "Single" jumper > > configuration option available? > > I'm not sure what a "Single" jumper is, but the drive is jumpered as > "master". The only options are "master", "slave", and "Cable Select". It's a jumper configuration that's commonly found on Western Digital IDE drives. It might also be labelled "Master w/o slave". Weirdness occurs (I've seen write errors and timeouts) when these drives sit on an otherwise empty IDE channel while they are set as 'master'. > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/ >