From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <tvrtko@ursulin.net>
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 K2TInKCJUhpm for <dm-crypt@saout.de>;
 Mon, 29 Oct 2012 21:14:18 +0100 (CET)
Received: from mail-ea0-f178.google.com (mail-ea0-f178.google.com
 [209.85.215.178])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (No client certificate requested)
 by mail.saout.de (Postfix) with ESMTPS
 for <dm-crypt@saout.de>; Mon, 29 Oct 2012 21:14:17 +0100 (CET)
Received: by mail-ea0-f178.google.com with SMTP id d13so2238927eaa.37
 for <dm-crypt@saout.de>; Mon, 29 Oct 2012 13:14:17 -0700 (PDT)
Message-ID: <508EE395.9010709@ursulin.net>
Date: Mon, 29 Oct 2012 20:14:13 +0000
From: Tvrtko Ursulin <tvrtko@ursulin.net>
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> <508ED985.5060301@ursulin.net>
 <508EDD6E.7030908@gmail.com>
In-Reply-To: <508EDD6E.7030908@gmail.com>
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: Milan Broz <gmazyland@gmail.com>
Cc: dm-crypt@saout.de, okozina@redhat.com, linux-kernel@vger.kernel.org

On 29/10/12 19:47, Milan Broz wrote:
> On 10/29/2012 08:31 PM, Tvrtko Ursulin wrote:
>> Just tried 3.6.4 and it is still broken. Is there anything else I could
>> try to debug this?
>
> See response from response from Ondra on dmcrypt list - your kernel config
> is perhaps broken.

I don't think that reached me - perhaps I was not copied.

Weird yes, I mean no one can spot anything bad with my config...

> Please use fresh checkout, run make oldconfig and try again.
> (Many people use 3.6 already and there is no other report.)

... and I just used it today to configure a fresh 3.6.4 (plus -rt10 
patches) without a problem.

Unless RT patchset is the culprit. Hm.. that would be unexpected, but I 
guess it is worth a shot. I'll let you know what happens without -rt.

Thanks,

Tvrtko