From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by mail.saout.de (Postfix) with ESMTP for ; Fri, 12 Nov 2010 22:01:05 +0100 (CET) Message-ID: <4CDDAB0C.1020603@redhat.com> Date: Fri, 12 Nov 2010 22:01:00 +0100 From: Milan Broz MIME-Version: 1.0 References: <20101112165136.GA23352@tansi.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] system freezes when using swap that is encrypted List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Nicolas Bock Cc: dm-crypt@saout.de On 11/12/2010 08:32 PM, Nicolas Bock wrote: > As an aside, would it make sense to go back in kernel versions to a time before these write-barriers? Do I need those anyway? Where they introduced recently? I don't think that barriers should be problem here, but everything is possible:-) How is that swap configured - through /etc/crypttab? (send dmsetup table; mount ) When it freezes, can you try to get full process backtrace and sent it to me? Just run "echo t>/proc/sysrq-trigger" or activate sysrq and do it from keybuard (alt-sysrq+t), (maybe serial console is needed here, but it should print status to syslog) Milan