From owner-freebsd-stable@FreeBSD.ORG Tue Sep 30 23:51:50 2008 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 54EAD1065689 for ; Tue, 30 Sep 2008 23:51:50 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id 045758FC16 for ; Tue, 30 Sep 2008 23:51:49 +0000 (UTC) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smarthost1.sentex.ca (8.14.3/8.14.3) with ESMTP id m8UNpkSw073873; Tue, 30 Sep 2008 19:51:46 -0400 (EDT) (envelope-from mike@sentex.net) Received: from mdt-xp.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.8/8.13.3) with ESMTP id m8UNpjs7024916 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 30 Sep 2008 19:51:46 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <200809302351.m8UNpjs7024916@lava.sentex.ca> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Tue, 30 Sep 2008 19:51:41 -0400 To: "Fernan Aguero" , freebsd-stable@freebsd.org From: Mike Tancsa In-Reply-To: <520894aa0809301434h68b94628x54ec08fd48785feb@mail.gmail.co m> References: <520894aa0809301434h68b94628x54ec08fd48785feb@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Scanned-By: MIMEDefang 2.64 on 64.7.153.18 Cc: Subject: Re: [FreeBSD] Fix for ServerWorks HT1000 in upcoming 7.1? 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: Tue, 30 Sep 2008 23:51:50 -0000 At 05:34 PM 9/30/2008, Fernan Aguero wrote: >I've been following the "HT1000 chipset errata saga" thread, and the >commits by sos@ to CVS (around Jan 2008), but have not seen other more >recent posts about this issue ... is it because it's already fixed and >working fine for everyone? > >http://lists.freebsd.org/pipermail/freebsd-current/2008-March/084272.html Yes, we ran into this yesterday on a fresh install using the 7.1 beta CD as it was set to PATA mode by accident. Also, on some earlier BIOS revs, we had to turn off "enable USB legacy mode" as well as "EHCI handoff". By default we set those to disabled as it seems to sometimes create a high interrupt load on the USB bus if its enabled. If you forget to set the mode to SATA, the dmesg will look like Sep 30 13:37:08 dev2 kernel: ad4: DMA limited to UDMA33, device found non-ATA66 cable Sep 30 13:37:08 dev2 kernel: ad4: 152627MB at ata2-master UDMA33 and you will indeed get corruption Turning onto normal SATA mode in the BIOS, you should see Sep 30 16:14:15 dev2 kernel: ad4: 152627MB at ata2-master SATA150 ... And everything works great. atapci0@pci0:1:14:0: class=0x010405 card=0x024a1166 chip=0x024a1166 rev=0x00 hdr=0x00 vendor = 'ServerWorks (Was: Reliance Computer Corp)' device = 'BCM5785 (HT1000) SATA Native SATA Mode' class = mass storage subclass = RAID cap 07[60] = PCI-X 64-bit supports 133MHz, 512 burst read, 8 split transactions cap 01[90] = powerspec 2 supports D0 D3 current D0 cap 05[a0] = MSI supports 1 message Start with ftp://ftp.freebsd.org//pub/FreeBSD/releases/i386/ISO-IMAGES/7.1/7.1-BETA-i386-disc1.iso ---Mike