From owner-freebsd-bugs@FreeBSD.ORG Wed Oct 31 13:20:04 2007 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6205D16A468 for ; Wed, 31 Oct 2007 13:20:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 5002513C4B5 for ; Wed, 31 Oct 2007 13:20:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.1/8.14.1) with ESMTP id l9VDK4iO034984 for ; Wed, 31 Oct 2007 13:20:04 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.1/8.14.1/Submit) id l9VDK3GN034983; Wed, 31 Oct 2007 13:20:03 GMT (envelope-from gnats) Date: Wed, 31 Oct 2007 13:20:03 GMT Message-Id: <200710311320.l9VDK3GN034983@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Alexander Sabourenkov Cc: Subject: Re: kern/115337: [ata] Promise SATA300 TX4 breaks with zfs in 7.0-current X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Alexander Sabourenkov List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 13:20:04 -0000 The following reply was made to PR kern/115337; it has been noted by GNATS. From: Alexander Sabourenkov To: bug-followup@FreeBSD.org Cc: ss.alert@online.no Subject: Re: kern/115337: [ata] Promise SATA300 TX4 breaks with zfs in 7.0-current Date: Wed, 31 Oct 2007 13:57:45 +0300 I'm currently working on this, after fixing similar issue in Linux. See this: http://lists.freebsd.org/pipermail/freebsd-stable/2007-October/037795.html After second glance on the code it now seems that the way to go is to make an ata_promise_begin_transaction() modeled after ata_ahci_begin_transaction(). If you have any comments on how to proceed with implementing the workaround, please let me know. -- ./lxnt