From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <okozina@redhat.com>
Received: from mail.saout.de ([127.0.0.1])
 by localhost (mail.saout.de [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id 2iGdApB4-Q1F for <dm-crypt@saout.de>;
 Mon, 22 Oct 2012 16:43:01 +0200 (CEST)
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28])
 by mail.saout.de (Postfix) with ESMTP
 for <dm-crypt@saout.de>; Mon, 22 Oct 2012 16:43:01 +0200 (CEST)
Received: from int-mx01.intmail.prod.int.phx2.redhat.com
 (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11])
 by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q9MERZv0005136
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK)
 for <dm-crypt@saout.de>; Mon, 22 Oct 2012 10:27:36 -0400
Received: from [10.34.131.67] (dhcp131-67.brq.redhat.com [10.34.131.67] (may
 be forged))
 by int-mx01.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id
 q9MERYrW025559
 for <dm-crypt@saout.de>; Mon, 22 Oct 2012 10:27:35 -0400
Message-ID: <508557D5.9000301@redhat.com>
Date: Mon, 22 Oct 2012 16:27:33 +0200
From: Ondrej Kozina <okozina@redhat.com>
MIME-Version: 1.0
References: <50830D33.5050807@ursulin.net> <5083C61C.5090807@gmail.com>
 <5083E4A8.3060501@ursulin.net> <5083E87B.2080908@gmail.com>
 <5083EC61.8070505@ursulin.net> <50844D01.9090805@gmail.com>
 <5084551E.5040304@ursulin.net>
In-Reply-To: <5084551E.5040304@ursulin.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [dm-crypt] cryptsetup not working under 3.6 - regression from
 3.4?
List-Id: <dm-crypt.saout.de>
List-Unsubscribe: <http://www.saout.de/mailman/options/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=unsubscribe>
List-Archive: <http://www.saout.de/pipermail/dm-crypt/>
List-Post: <mailto:dm-crypt@saout.de>
List-Help: <mailto:dm-crypt-request@saout.de?subject=help>
List-Subscribe: <http://www.saout.de/mailman/listinfo/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=subscribe>
To: dm-crypt@saout.de

Hi,

On 10/21/2012 10:03 PM, Tvrtko Ursulin wrote:
>>
>> Hm, so it should work without problem. Can you paste full output of failing
>> cryptsetup command (with added --debug switch) and your full kernel .config?
>
> Attached.

are you sure the attached kernel .config is the correct one? I haven't 
been able to compile the kernel with it at all. It reports: "unmet 
direct dependencies" so it doesn't look as valid config file to kernel 
3.6.1 to me. On the other hand, there's 3.6.1 kernel mentioned in the 
.config header. It looks to me the file is somehow messy.

Anyway If I run make oldconfig over the supplied .config file, 
everything works fine for me.

With regards
Ondrej