Date: Fri, 17 Dec 2010 17:37:36 -0500 From: jhell <jhell@DataIX.net> To: Mike Tancsa <mike@sentex.net> Cc: Kostik Belousov <kostikbel@gmail.com>, Jan Henrik Sylvester <me@janh.de>, stable-list freebsd <freebsd-stable@freebsd.org> Subject: Re: aesni(?) corrupts data on 8.2-BETA1 Message-ID: <4D0BE630.6010900@DataIX.net> In-Reply-To: <4D0B6D26.7030808@sentex.net> 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> <4D0B6D26.7030808@sentex.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12/17/2010 09:01, Mike Tancsa wrote: > 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 I can simply run a scrub on the pool and within a little while within 12% - 18% it goes ker-plunk!. Not that it really has to do with the percentage rage as it does the timing. I do have prefetch enabled when this happens and currently running with it turned off and will booting so said kernel.bad in a little while to see if that makes a difference. -- jhell,v
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D0BE630.6010900>