From owner-freebsd-questions@FreeBSD.ORG Tue Jun 5 17:17:51 2007 Return-Path: X-Original-To: questions@freebsd.org Delivered-To: freebsd-questions@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 35FDF16A46B for ; Tue, 5 Jun 2007 17:17:51 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from mail-out3.apple.com (mail-out3.apple.com [17.254.13.22]) by mx1.freebsd.org (Postfix) with ESMTP id 1BB7313C4B0 for ; Tue, 5 Jun 2007 17:17:51 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from relay5.apple.com (relay5.apple.com [17.128.113.35]) by mail-out3.apple.com (Postfix) with ESMTP id 320C77F6B96; Tue, 5 Jun 2007 09:59:27 -0700 (PDT) Received: from relay5.apple.com (unknown [127.0.0.1]) by relay5.apple.com (Symantec Mail Security) with ESMTP id 8689929C006; Tue, 5 Jun 2007 10:00:21 -0700 (PDT) X-AuditID: 11807123-9f821bb000000a23-38-466596a5ea49 Received: from [17.214.13.96] (cswiger1.apple.com [17.214.13.96]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by relay5.apple.com (Apple SCV relay) with ESMTP id 7295630400D; Tue, 5 Jun 2007 10:00:21 -0700 (PDT) In-Reply-To: <798114.3933.qm@web34504.mail.mud.yahoo.com> References: <798114.3933.qm@web34504.mail.mud.yahoo.com> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <8229DFF3-1298-4692-A6CC-886EC2E97730@mac.com> Content-Transfer-Encoding: 7bit From: Chuck Swiger Date: Tue, 5 Jun 2007 10:00:20 -0700 To: N. Harrington X-Mailer: Apple Mail (2.752.2) X-Brightmail-Tracker: AAAAAA== Cc: questions@freebsd.org Subject: Re: How to solve mysterious system lockups? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jun 2007 17:17:51 -0000 On Jun 4, 2007, at 8:49 PM, N. Harrington wrote: > Hi Garret > Here is the driver info. > > -- SATA > > atapci0: port > 0xbc00-0xbc07,0xb400-0xb403,0xb000-0xb007,0xac00-0xac03,0xa800-0xa80f Ah-- regrettably, the Silicon Image 3112 & 3114 chips have some significant hardware defects, which tend to show up more frequently when you put the disk system under significant load (especially RAID). It's likely to be the case that switching to a better SATA controller would resolve the problems you are seeing with your SATA- based machines. If you have a chance, perhaps see whether building a kernel with the following patch does anything to help the "disk lockups" you've seen: --- sys/dev/ataata-chipset.c~ Wed Jun 1 14:24:26 2005 +++ sys/dev/ataata-chipset.c Tue Jun 5 12:54:58 2007 @@ -2240,7 +2240,7 @@ struct ata_pci_controller *ctlr = device_get_softc(dev); struct ata_chip_id *idx; static struct ata_chip_id ids[] = - {{ ATA_SII3114, 0x00, SIIMEMIO, SII4CH, ATA_SA150, "SiI 3114" }, + {{ ATA_SII3114, 0x00, SIIMEMIO, (SII4CH|SIIBUG), ATA_SA150, "SiI 3114" }, { ATA_SII3512, 0x02, SIIMEMIO, 0, ATA_SA150, "SiI 3512" }, { ATA_SII3112, 0x02, SIIMEMIO, 0, ATA_SA150, "SiI 3112" }, { ATA_SII3112_1, 0x02, SIIMEMIO, 0, ATA_SA150, "SiI 3112" }, The effect of this change is to limit the SilI controller into doing DMA transfers which are smaller than 8KB, which seems to mitigate the most significant problems with the chipset, at the cost of some performance. -- -Chuck