From owner-freebsd-current@FreeBSD.ORG Thu Jul 10 02:25:29 2008 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 C639A1065829; Thu, 10 Jul 2008 02:25:29 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from server.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id D58428FC18; Thu, 10 Jul 2008 02:25:28 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from localhost.corp.yahoo.com (john@localhost [IPv6:::1]) (authenticated bits=0) by server.baldwin.cx (8.14.2/8.14.2) with ESMTP id m6A2OvAx028341; Wed, 9 Jul 2008 22:25:22 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: gnn@FreeBSD.org Date: Wed, 9 Jul 2008 22:09:35 -0400 User-Agent: KMail/1.9.7 References: <200807041521.25711.jhb@freebsd.org> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200807092209.35780.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [IPv6:::1]); Wed, 09 Jul 2008 22:25:22 -0400 (EDT) X-Virus-Scanned: ClamAV 0.93.1/7680/Wed Jul 9 19:31:16 2008 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00,NO_RELAYS autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: freebsd-current@FreeBSD.org Subject: Re: Has anyone else seen any form of in memory or on disk corruption? 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: Thu, 10 Jul 2008 02:25:30 -0000 On Saturday 05 July 2008 12:15:16 pm gnn@freebsd.org wrote: > At Fri, 4 Jul 2008 15:21:25 -0400, > John Baldwin wrote: > > > > If this is one of the ATA controllers where it tries to use 63k > > transfers (126 * DEV_BSIZE) instead of 64k, then change it to 32k > > (64 * DEV_BSIZE). W/o this fix I see massive data corruption > > (couldn't even build a kernel with the fix, had to reinstall the > > box) on HT1000 ATA chipsets. Crashdumps also don't seem to work > > reliably w/o changing that. > > > > Hmm, I don't see quite that much corruption. > > Reading over ata-chipset.c I see that there are 4 controllers which > may have this issue: > > Cyrix > Marvell > National > Serverworks > > This has been happening on AMCC cards and very occasionally Supermicro > motherboards. Is there an easy way to determine if either of those > are using these chips? PCI device IDs of the atapciX devices (and see if they match up with what devices use the chipset routines that set '126 * DEV_BSIZE' -- John Baldwin