From owner-freebsd-stable@FreeBSD.ORG Fri Dec 17 14:01:14 2010 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 3FB4D1065674 for ; Fri, 17 Dec 2010 14:01:14 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1-6.sentex.ca [IPv6:2607:f3e0:0:1::12]) by mx1.freebsd.org (Postfix) with ESMTP id EA0838FC16 for ; Fri, 17 Dec 2010 14:01:13 +0000 (UTC) Received: from [IPv6:2607:f3e0:0:4:5022:4efd:b73a:4846] ([IPv6:2607:f3e0:0:4:5022:4efd:b73a:4846]) by smarthost1.sentex.ca (8.14.4/8.14.4) with ESMTP id oBHE1A76099177 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 17 Dec 2010 09:01:11 -0500 (EST) (envelope-from mike@sentex.net) Message-ID: <4D0B6D26.7030808@sentex.net> Date: Fri, 17 Dec 2010 09:01:10 -0500 From: Mike Tancsa User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: jhell References: <4D02CA9E.1030704@janh.de> <4D02D736.7000103@sentex.net> <20101211160121.GL33073@deviant.kiev.zoral.com.ua> <4D040458.3030601@sentex.net> <20101211232253.GR33073@deviant.kiev.zoral.com.ua> <4D04195F.1080802@sentex.net> <20101212084327.GS33073@deviant.kiev.zoral.com.ua> <4D0AB882.5090800@DataIX.net> <4D0AB987.5090000@DataIX.net> In-Reply-To: <4D0AB987.5090000@DataIX.net> X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.67 on IPv6:2607:f3e0:0:1::12 Cc: Kostik Belousov , Jan Henrik Sylvester , stable-list freebsd Subject: Re: aesni(?) corrupts data on 8.2-BETA1 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: Fri, 17 Dec 2010 14:01:14 -0000 On 12/16/2010 8:14 PM, jhell wrote: > On 12/16/2010 20:10, jhell wrote: >> Regarding this patch(r216455) and r216162 I have had to back both of >> them out of my local tree to avoid panics on a ZFS & UFS2 i386 system. I have zfs & UFS on AMD64 and have not seen any issues. How do you trigger the issue in i386 ? Or does it just randomly happen ? ---Mike