From owner-freebsd-stable@FreeBSD.ORG Fri Mar 12 19:11:33 2010 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 26253106567F for ; Fri, 12 Mar 2010 19:11:33 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-fx0-f223.google.com (mail-fx0-f223.google.com [209.85.220.223]) by mx1.freebsd.org (Postfix) with ESMTP id A7B7E8FC14 for ; Fri, 12 Mar 2010 19:11:32 +0000 (UTC) Received: by fxm23 with SMTP id 23so1526864fxm.3 for ; Fri, 12 Mar 2010 11:11:31 -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=q5K8/dNMlZQgEuSV+5KgroWCLsu9ntzGcUK5JnS8ZRU=; b=rpLPuX/WZHnhxqhyLZtY/CvNmDe1/QDh1vqUOQ2+neUuZbali8vsaLA/AFHCjb6aKS O7A+9qn0N2i5PKoC6HyKk4kXY6+pnRW07JucCPm4JQBBf2M1v+QOMBnQbUs3kAYVijNe /yHICmIWXn61ee/PCataTZ3wGJn1PqxitAIig= 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=NB+BDbmqe3ZnhGFk48+WxrSSMoXo3wMDOKadgN2j9gheaxPpzcibuPe2XMrEf+MCNB GLsFM983epNFBb47VhCelWoMXaw0umfqQu9QfXYTrdiThukGc3lngSkgfYDaSrrYTvRw qmKE+GsJafFg0QELMaPuE49qK69dSsuHNnSk0= Received: by 10.223.60.142 with SMTP id p14mr2292154fah.47.1268421091630; Fri, 12 Mar 2010 11:11:31 -0800 (PST) Received: from mavbook.mavhome.dp.ua (s224.GtokyoFL6.vectant.ne.jp [222.228.90.224]) by mx.google.com with ESMTPS id 16sm1227698fxm.11.2010.03.12.11.11.29 (version=SSLv3 cipher=RC4-MD5); Fri, 12 Mar 2010 11:11:31 -0800 (PST) Sender: Alexander Motin Message-ID: <4B9A8F14.4030907@FreeBSD.org> Date: Fri, 12 Mar 2010 20:59:32 +0200 From: Alexander Motin User-Agent: Thunderbird 2.0.0.23 (X11/20091212) MIME-Version: 1.0 To: Jeremy Chadwick References: <20100312121409.GA79294@fasterix.frmug.org> <20100312131832.GA54731@icarus.home.lan> <20100312165744.GA86971@fasterix.frmug.org> <20100312170936.GA59343@icarus.home.lan> In-Reply-To: <20100312170936.GA59343@icarus.home.lan> X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, Pierre Beyssac Subject: Re: (fixed) Re: 8-STABLE interrupt storm on atapci(?), Dell Inspiron 580 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: Fri, 12 Mar 2010 19:11:33 -0000 Jeremy Chadwick wrote: > On Fri, Mar 12, 2010 at 05:57:44PM +0100, Pierre Beyssac wrote: >>> Possibly this is the source of the problem (specifically, it looks like >>> FreeBSD doesn't have proper device ID knowledge of what this controller >>> is. I believe that's because this system is *very* new, a Core i3/i5/i7 >>> system)? >> I didn't notice that, you're right! The system is brand new, got >> it delivered on Tuesday. Another odd thing is that the controllers >> have differents IDs, 0x3b208086 vs 0x3b268086. >> >> I added the IDs to ata-intel.c and it fixes the problem. >> >> Preparing a patch. Thanks for the hint! >> -- >> Pierre Beyssac pb@fasterix.frmug.org > >> --- ata-intel.c.orig 2010-03-12 17:02:00.680011011 +0100 >> +++ ata-intel.c 2010-03-12 16:55:54.773702505 +0100 >> @@ -156,6 +156,8 @@ >> { 0x3a2d8086, 0, INTEL_AHCI, 0, ATA_SA300, "PCH" }, >> { 0x3a2e8086, 0, INTEL_AHCI, 0, ATA_SA300, "PCH" }, >> { 0x3a2f8086, 0, INTEL_AHCI, 0, ATA_SA300, "PCH" }, >> + { 0x3b208086, 0, INTEL_AHCI, 0, ATA_SA300, "PCH" }, >> + { 0x3b268086, 0, INTEL_AHCI, 0, ATA_SA300, "PCH" }, >> { ATA_I31244, 0, 0, 2, ATA_SA150, "31244" }, >> { ATA_ISCH, 0, 0, 1, ATA_UDMA5, "SCH" }, >> { 0, 0, 0, 0, 0, 0}}; > > I had a chance to review the Intel 5 Series and 3400 Series Chipset > document, which is specific to the PCH. The breakdown for those > two Device IDs, under Vendor ID 0x8086 (Intel), is: > > Device ID 0x3b20 > - PCH SATA controller > - Desktop revision, non-AHCI and non-RAID Mode > - Ports 0,1,2,3 > > Device ID 0x3b26 > - PCH SATA controller > - Desktop revision, non-AHCI and non-RAID mode > - Ports 4,5 > > So I'm not sure the setting of the INTEL_AHCI flag there is correct > for these controllers. mav@ will need to chime in here. Except ICH6 Intel uses separate IDs for AHCI and non-AHCI SATA controller modes. So this flag is not completely correct. But probably it shoudn't be just removed, as it is checked in other place. I know about this and going to handle it later. It's not a problem now. > Regarding the "dual device IDs": what this means is that ports 0-3 are > tied to one device on the PCI bus, and ports 4-5 are tied to another > device on the PCI bus. They might have chosen to do this so they could > segregate which ports do what or operate differently somehow. > > mav@ may also want to review the specification since it mentions a bunch > of other Device IDs which don't appear to be in the above list: > > http://www.intel.com/Assets/PDF/specupdate/322170.pdf Thanks. PS: Check BIOS settings for enabling AHCI mode. -- Alexander Motin