From owner-freebsd-stable@FreeBSD.ORG Sat Dec 26 10:19:08 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 E3CA31065775; Sat, 26 Dec 2009 10:19:07 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-fx0-f227.google.com (mail-fx0-f227.google.com [209.85.220.227]) by mx1.freebsd.org (Postfix) with ESMTP id 4D1EA8FC1A; Sat, 26 Dec 2009 10:19:07 +0000 (UTC) Received: by fxm27 with SMTP id 27so9155421fxm.3 for ; Sat, 26 Dec 2009 02:19:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=LSrRbJ0z7BEAKX12UG0A9VZdFwrUTCGUJ2kWDPxL2tY=; b=u6MqBvjrmG9RglkraEfgLkhUUYbtPkrRMcVdkY5FK8ejAOIAJZAnGBJ7e8lFwG/St0 Uqj21jQJ0D3tiwi0+wMikZ3nrvuaNyPxcOSlcqPu7W1jIWhvO/I+IfNFIpvvLbczrhcy IAyM7ODrqUsiCGY5SGLd+++S0PZJXnM3pQFPw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=UblM/wXI+RSz8ILOeIV4ESZOa99pBjKU2odCGL2rSP3sP4Qjs6SypwbbGhEeB4QFt5 /+t4NpLeX/JWB/mh6ZaYYCq+5hicxnpxM5ytWkF6305EcTLUw3lr0svG5Ad3XKA6XmjM a9DzJlUAAcUI8kxEjW8StrBDrQordDkinX2KE= Received: by 10.223.144.195 with SMTP id a3mr5784538fav.103.1261822746238; Sat, 26 Dec 2009 02:19:06 -0800 (PST) Received: from mavbook.mavhome.dp.ua ([95.109.129.15]) by mx.google.com with ESMTPS id 13sm3407307fxm.1.2009.12.26.02.19.02 (version=SSLv3 cipher=RC4-MD5); Sat, 26 Dec 2009 02:19:05 -0800 (PST) Sender: Alexander Motin Message-ID: <4B35E313.1020204@FreeBSD.org> Date: Sat, 26 Dec 2009 12:18:59 +0200 From: Alexander Motin User-Agent: Thunderbird 2.0.0.23 (X11/20091212) MIME-Version: 1.0 To: Nathan Lay References: <1261707782.00199010.1261696205@10.7.7.3> <4B346BE0.2010909@FreeBSD.org> <4B357CC4.9020909@comcast.net> In-Reply-To: <4B357CC4.9020909@comcast.net> X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: 8-STABLE ahci fails to attach, does not fallback on ataahci 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, 26 Dec 2009 10:19:08 -0000 Nathan Lay wrote: >> This patch should fix the issue: >> --- ahci.c.prev 2009-12-08 13:27:31.000000000 +0200 >> +++ ahci.c 2009-12-25 09:28:32.000000000 +0200 >> @@ -115,8 +115,8 @@ static struct { >> {0x43931002, "ATI IXP700", 0}, >> {0x43941002, "ATI IXP800", 0}, >> {0x43951002, "ATI IXP800", 0}, >> - {0x26528086, "Intel ICH6", 0}, >> - {0x26538086, "Intel ICH6M", 0}, >> + {0x26528086, "Intel ICH6", AHCI_Q_NOFORCE}, >> + {0x26538086, "Intel ICH6M", AHCI_Q_NOFORCE}, >> {0x26818086, "Intel ESB2", 0}, >> {0x26828086, "Intel ESB2", 0}, >> {0x26838086, "Intel ESB2", 0}, >> > I also noticed in dmesg that ataahci never actually attaches (There's no > AHCI messages). I examined ahci.c and ata-ahci.c and noticed that > ata-ahci.c lacks the quirk table and code in ata_ahci_probe that would > normally match this chip in ahci_probe. It is actually more correct, but less effective approach. Theoretically BIOS should configure controller to report SATA subclass and AHCI progif. But as soon as not all BIOS'es able to do that, that array of quirks used. But that quirk approach is not working fine (complicated and vendor-specific) for Intel chipsets, so I have added NOFORCE quirk, needed to fix your problem. > I think that it's subclass > isn't PCIS_STORAGE_SATA. I tried to hardcode it to see if it would work > but I never successfully persuaded ataahci to attach. I'm not familiar > with kernel debugging or development and grew weary of constantly > recompiling the kernel to try things. You should first talk to you BIOS. If it is able to enable AHCI - you are lucky. Else it is not solvable without dirty vendor-specific code, messing resource management, as now your controller is not providing resources needed for AHCI operation. -- Alexander Motin