From owner-freebsd-current@FreeBSD.ORG Fri Jan 29 14:37:43 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 648AA106566B for ; Fri, 29 Jan 2010 14:37:43 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-bw0-f213.google.com (mail-bw0-f213.google.com [209.85.218.213]) by mx1.freebsd.org (Postfix) with ESMTP id B90D18FC1F for ; Fri, 29 Jan 2010 14:37:42 +0000 (UTC) Received: by bwz5 with SMTP id 5so1451240bwz.3 for ; Fri, 29 Jan 2010 06:37:41 -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=Oaq7Hu/Q3VKk+dOw9Z8TN9EIOnWycblH6WDuwpqhOv4=; b=vngB6T82B3cUfgmgX4kHAlBBhZteFy9a0cAXmnsnTru2WBIa6nLJmOj+UUyGwnkRIU aMKoK+hcffEF3zK8JDwvVtSPGT4b0E/clTzaoppoU7QneMoQc/eXR6c9OJGnMaGVEx61 VBkqtML/G57rg371sbyybDopYzmTqz7ZEeXFA= 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=xHXYobyYZqvEB1Z+ofH/Zpz+onUsvFlL2hKY4hNGzgNfTtOHosRPI7yg/xNeXHJamr PZB7SgI0W9dZPHEIEmSuDwX0z5q+5bvdH/S0GwYLthL2ZZLkhyvYUNtgn4HrTkJtNCsv LXKTBlnszpBG/K6qKZshmqaNmppNSV8sE4vFo= Received: by 10.103.80.15 with SMTP id h15mr418927mul.54.1264775861552; Fri, 29 Jan 2010 06:37:41 -0800 (PST) Received: from mavbook.mavhome.dp.ua (pc.mavhome.dp.ua [212.86.226.226]) by mx.google.com with ESMTPS id y37sm5661538mug.38.2010.01.29.06.37.38 (version=SSLv3 cipher=RC4-MD5); Fri, 29 Jan 2010 06:37:38 -0800 (PST) Sender: Alexander Motin Message-ID: <4B62F2B0.2030704@FreeBSD.org> Date: Fri, 29 Jan 2010 16:37:36 +0200 From: Alexander Motin User-Agent: Thunderbird 2.0.0.23 (X11/20091212) MIME-Version: 1.0 To: Andriy Gapon References: <4B55D9D4.1000008@FreeBSD.org> <4B61C688.2050609@FreeBSD.org> <4B61CCB6.4040005@FreeBSD.org> <4B62C97F.7080000@FreeBSD.org> <4B62EDFB.1060103@icyb.net.ua> In-Reply-To: <4B62EDFB.1060103@icyb.net.ua> X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@FreeBSD.org, Yamagi Burmeister Subject: Re: Pack of CAM improvements X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Fri, 29 Jan 2010 14:37:43 -0000 Andriy Gapon wrote: > on 29/01/2010 13:41 Alexander Motin said the following: >> Yamagi Burmeister wrote: >>> On Thu, 28 Jan 2010, Alexander Motin wrote: >>> >>>>>> Yamagi Burmeister wrote: >>>>>>> ahcich0: is 00000002 cs 00000000 ss 00000000 rs 00000001 tfd 50 serr >>>>>>> 00000000 >>>>>>> ahcich0: Timeout on slot 0 >>>>>> Try to disable MSI interrupts with `hint.ahci.0.msi=0`. >>>>> That fixed the problem. Thank you :) >>>> That's quite strange, as in many other cases IXP700 is working fine. >>>> Different revisions? What is your `pciconf -lvbc` reports? >>> When I helped nox@ debugging a problem with timeouts we noticed, that >>> our controlers are of differend revisions. The pciconf output ist: >>> >>> ahci0@pci0:0:17:0: class=0x010601 card=0x43911002 chip=0x43911002 >>> rev=0x00 hdr=0x00 >>> vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' >>> device = 'SB700 SATA Controller [AHCI mode]' >>> class = mass storage >>> subclass = SATA >>> bar [10] = type I/O Port, range 32, base 0xd000, size 8, enabled >>> bar [14] = type I/O Port, range 32, base 0xc000, size 4, enabled >>> bar [18] = type I/O Port, range 32, base 0xb000, size 8, enabled >>> bar [1c] = type I/O Port, range 32, base 0xa000, size 4, enabled >>> bar [20] = type I/O Port, range 32, base 0x9000, size 16, enabled >>> bar [24] = type Memory, range 32, base 0xfe8ff800, size 1024, >>> enabled >>> cap 01[60] = powerspec 2 supports D0 D3 current D0 >>> cap 05[50] = MSI supports 4 messages, 64 bit >>> cap 12[70] = SATA Index-Data Pair >> What's interesting, is that Asus board with the same chipset doesn't >> expose MSI support at all: >> >> ahci0@pci0:0:17:0: class=0x010601 card=0x43911002 chip=0x43911002 >> rev=0x00 hdr=0x00 >> vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' >> device = 'SB700 SATA Controller [AHCI mode]' >> class = mass storage >> subclass = SATA >> bar [10] = type I/O Port, range 32, base 0xc000, size 8, enabled >> bar [14] = type I/O Port, range 32, base 0xb000, size 4, enabled >> bar [18] = type I/O Port, range 32, base 0xa000, size 8, enabled >> bar [1c] = type I/O Port, range 32, base 0x9000, size 4, enabled >> bar [20] = type I/O Port, range 32, base 0x8000, size 16, enabled >> bar [24] = type Memory, range 32, base 0xfbcffc00, size 1024, enabled >> cap 01[60] = powerspec 2 supports D0 D3 current D0 >> cap 12[70] = SATA Index-Data Pair >> > > PCI revision register of SMBus device (0:20:0) gives a particular revision of SB7x0. > SB700 RPR document (section 7.11) says that MSI capability should be disabled if > the revision is 0x39 or 0x3a, it should be enabled for newer revisions (0x3b, 03c). VIA uses ISA bridge to identify chipset, ATI (as you said) - SMBus. Hell! Why not to do it properly? > Those who like to experiment with potentially dangerous things may try playing > with bit 16 of PCI config register 0x50 of SATA controller device. I would prefer it was done by BIOS. Probably ASUS did it, as my board has 0x3a. -- Alexander Motin