From owner-freebsd-i386@FreeBSD.ORG Fri Mar 4 20:20:19 2005 Return-Path: Delivered-To: freebsd-i386@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3454D16A4CE for ; Fri, 4 Mar 2005 20:20:19 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 14C4143D3F for ; Fri, 4 Mar 2005 20:20:19 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id j24KKIEU075929 for ; Fri, 4 Mar 2005 20:20:18 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id j24KKIuS075928; Fri, 4 Mar 2005 20:20:18 GMT (envelope-from gnats) Date: Fri, 4 Mar 2005 20:20:18 GMT Message-Id: <200503042020.j24KKIuS075928@freefall.freebsd.org> To: freebsd-i386@FreeBSD.org From: "Schlake (William Colburn)" Subject: Re: i386/77643: SATA PCI controllers fail with WRITE_DMA errors under GMIRROR X-BeenThere: freebsd-i386@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: "Schlake \(William Colburn\)" List-Id: I386-specific issues for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Mar 2005 20:20:19 -0000 The following reply was made to PR i386/77643; it has been noted by GNATS. From: "Schlake (William Colburn)" To: freebsd-gnats-submit@FreeBSD.org, karl@FS.denninger.net Cc: Subject: Re: i386/77643: SATA PCI controllers fail with WRITE_DMA errors under GMIRROR Date: Fri, 4 Mar 2005 13:18:04 -0700 I just got 2 new disks and an adaptec controller at my house. After a couple of crashes, and a verification that none of my cables were bad, I checked the known bugs. I'm running a 5.4-PRERELEASE from Wednesday morning (I'm not at home so I can't get you the specifics). Not mounting the gmirrored SATA drives connected to the motherboard seems to have made me crash free, but now I'm short 170GB of disk. Since this bug seems to have little going on with it I thought I would add another datapoint that the problem seems to exist. The new data that I can add to the bug is that my machine currently has the mirrored disks on the PCI SATA card and no disks mounted on the motherboard SATA, and I did not manage to tweak a crash by reading/writing to the disk. The only crashes I had were when I was copying data from the original mirror on the motherboard to the new mirror on the PCI card. -- void *(*(*schlake(void *))[])(void *);