From owner-freebsd-stable@FreeBSD.ORG Thu Nov 19 08:53:27 2009 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 0B5981065670 for ; Thu, 19 Nov 2009 08:53:27 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from QMTA13.emeryville.ca.mail.comcast.net (qmta13.emeryville.ca.mail.comcast.net [76.96.27.243]) by mx1.freebsd.org (Postfix) with ESMTP id E5B3A8FC12 for ; Thu, 19 Nov 2009 08:53:26 +0000 (UTC) Received: from OMTA13.emeryville.ca.mail.comcast.net ([76.96.30.52]) by QMTA13.emeryville.ca.mail.comcast.net with comcast id 6wr41d00317UAYkADwtTw9; Thu, 19 Nov 2009 08:53:27 +0000 Received: from koitsu.dyndns.org ([98.248.46.159]) by OMTA13.emeryville.ca.mail.comcast.net with comcast id 6wtS1d0053S48mS8ZwtSVP; Thu, 19 Nov 2009 08:53:27 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 4A5F81E3035; Thu, 19 Nov 2009 00:53:25 -0800 (PST) Date: Thu, 19 Nov 2009 00:53:25 -0800 From: Jeremy Chadwick To: freebsd-stable@freebsd.org Message-ID: <20091119085325.GA35228@icarus.home.lan> References: <4B03322A.2080608@FreeBSD.org> <4B038E75.1010501@rdtc.ru> <20091118061726.GA1675@icarus.home.lan> <4B04B908.1020505@rdtc.ru> <4B05005D.9040706@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4B05005D.9040706@FreeBSD.org> User-Agent: Mutt/1.5.20 (2009-06-14) Subject: Re: HEADS UP: major CAM ATA MFC 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: Thu, 19 Nov 2009 08:53:27 -0000 On Thu, Nov 19, 2009 at 10:22:53AM +0200, Alexander Motin wrote: > Eugene Grosbein wrote: > > Jeremy Chadwick wrote: > >> I didn't have this problem. System has AHCI in use, and the kernel is > >> built to make use of modular atacore. Specifically: > >> > >> # Modular ATA > >> device atacore # Core ATA functionality > >> device ataisa # ISA bus support > >> device atapci # PCI bus support; only generic chipset support > >> device ataahci # AHCI SATA > >> device ataintel # Intel > > > > How should STABLE user (not tracking freebsd-current@) learn about CAM ATA configuration? > > There is ahci(4) manual page in 8.0-PRERELEASE but no ada(4) that is linked here. > > > > I've just tried "Modular ATA" configuration of Intel ICH7-based system plus "device ahci" > > minus all traditional ata(4) kernel configuration, the kernel builds fine > > but boot messages do not show any attempt to detect my SATA HDD, > > so root mount just fails (I use GEOM UFS labels in my /etc/fstab). > > Typing ? at "mounroot" prompt I see only daX devices standing for my USB cardreader > > and no device for HDD. > > Read ahci(4) carefully. It has all possible references. If you think it > is not enough, propose patches. I had no idea said details were in the ahci(4) man page, and I doubt the rest of the user community will know that either. There's also no man page for ada(4). There is some ambiguity in this part of the ahci(4) man page: AHCI hardware is also supported by ataahci driver from ata(4) subsystem. If both drivers are loaded at the same time, this one will be given precedence as the more functional of the two. The grammar here is very difficult to understand; "if both drivers" is too vague. The way this paragraph can be interpreted: - "If both drivers" could refer to ata(4) and ataahci - "If both drivers" could refer to ata(4) and ahci(4) - "If both drivers" could refer to ada(4) and ahci(4) - "If both drivers" could refer to ahci(4) and ata(4) I'll happily re-write the documentation for this if someone can take the time to explain what the paragraph actually is trying to say. Users are going to be very, very confused if there is a driver called ataahci and another driver called ahci. Finally, appropriate details need to be placed into the i386 and amd64 kernel configuration files; either in GENERIC (commented out) or in /sys/conf/NOTES. As it stands, there's nothing that informs anyone of this change, and if users are being pointed to the ahci(4) man page, they're going to get confused (see above). -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |