From owner-freebsd-stable@FreeBSD.ORG Sat Dec 11 01:43:32 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 AC9C2106564A for ; Sat, 11 Dec 2010 01:43:32 +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 680318FC12 for ; Sat, 11 Dec 2010 01:43:32 +0000 (UTC) Received: from [IPv6:2607:f3e0:0:4:2540:154a:ba54:4afb] ([IPv6:2607:f3e0:0:4:2540:154a:ba54:4afb]) by smarthost1.sentex.ca (8.14.4/8.14.4) with ESMTP id oBB1hUuF002806 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 10 Dec 2010 20:43:30 -0500 (EST) (envelope-from mike@sentex.net) Message-ID: <4D02D736.7000103@sentex.net> Date: Fri, 10 Dec 2010 20:43:18 -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: Jan Henrik Sylvester References: <4D02CA9E.1030704@janh.de> In-Reply-To: <4D02CA9E.1030704@janh.de> 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 , 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: Sat, 11 Dec 2010 01:43:32 -0000 Actually, I just noticed something like this as well with ssh via cryptodev and rsync as well. It was erroring out. eg. Dec 10 16:50:01 backup3 sshd[13120]: Corrupted MAC on input. Dec 10 16:50:01 backup3 sshd[13120]: Finished discarding for 64.x.x.x I had a few ssh sessions die as well. It was working ok with a kernel / world from last week. I was going to try and see if I can narrow it down, but it seemed to had been working fine with world from last week. Not sure if its the openssl update ? But if you are seeing issues with geli, then I doubt its openssl. ---Mike On 12/10/2010 7:49 PM, Jan Henrik Sylvester wrote: > I just upgraded my main laptop from 8.1-RELEASE (GENERIC, amd64) to > 8.2-BETA1 and added aesni_load="YES" to my /boot/loader.conf. > > (If my interpretation is correct:) With aesni loaded, I see many files > corrupted on my geli encrypted volume. Without aesni loaded, they are ok. > > I have got a journaling UFS2 on gjournal on geli on a FreeBSD partition > on a MBR slice on a disk with ahci loaded. > > Story: First I noticed some weirdness of Thunderbird not showing the > "upgraded" message properly and reloading IMAP messages that have > already been read, but did not think of anything. Only during my usual > rsyncing of the encrypted volume, I saw that some files could not be > read (invalid file descriptor?). I rebooted without aesni and got a > different error message. > > I created checksums of all files on that encrypted volume with and > without aesni loaded (rebooting in between): 150 Differences (one files > could not be read in both cases). > > Just to make sure, I tried to rsync with "--checksum" and "--dry-run" to > the other machine that is supposed to have the same files: With aesni, > many files were scheduled to be synced and one could not be read, but > without aesni, only that one file was scheduled to be synced -- it > probably got corrupted for good with aesni loaded. It is especially > weird that I did not attempt to write to the file that got corrupted on > disk with aesni loaded. > > Is there anything I am doing wrong or is it really aesni or the > processor failing? > > The processor is a Core i7-M620 (with AESNI of course). > > Before I investigate any further, I have to make a real backup... > rsyncing does not prevent silent corruption. I am lucky that it was not > so silent after all. > > Jan Henrik > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > >