From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gmazyland@gmail.com>
Received: from mail-wi0-x230.google.com (mail-wi0-x230.google.com
 [IPv6:2a00:1450:400c:c05::230])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (No client certificate requested)
 by mail.server123.net (Postfix) with ESMTPS
 for <dm-crypt@saout.de>; Mon,  4 May 2015 21:40:52 +0200 (CEST)
Received: by widdi4 with SMTP id di4so121631902wid.0
 for <dm-crypt@saout.de>; Mon, 04 May 2015 12:40:51 -0700 (PDT)
Message-ID: <5547CB40.5030506@gmail.com>
Date: Mon, 04 May 2015 21:40:48 +0200
From: Milan Broz <gmazyland@gmail.com>
MIME-Version: 1.0
References: <CADDQthuKj7zH-kT14WX4R0m85C_1ANng3Jp-ijSEtzg626yqFA@mail.gmail.com>	<5547C2F7.3000305@gmail.com>
 <CADDQthunCzm6tqai+iOV_kDJ-Ci_zarb1DOwgJ1zhMBsvXe+8Q@mail.gmail.com>
In-Reply-To: <CADDQthunCzm6tqai+iOV_kDJ-Ci_zarb1DOwgJ1zhMBsvXe+8Q@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: [dm-crypt] cryptsetup 1.6.2 hands on "waiting for zero"
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: Mrukant Popat <mrukant@gmail.com>
Cc: dm-crypt <dm-crypt@saout.de>

On 05/04/2015 09:29 PM, Mrukant Popat wrote:
> Hello Milan,
> 
> Thanks for the quick answer. I cross-compiled all the tools using yocto for iMX6 freescale.
> I read the information here  --> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=585786   and 
> here --> http://comments.gmane.org/gmane.linux.debian.devel.bugs.general/719712
> 
> and disabled udev  using /etc/init.d/udev stop.
> 
> After disabling udev, it seems to work. Could you provide the udev rules. Probably the reason is that I do not seem to have the udev rules. 

Udev rules are part of the device-mapper installation (part of lvm2 source code),
so check what version you are compiling and if udev is enabled, it should install these rules.

But AFAIK Debian still tries to reinvent the wheel and distributes own modified lvm2/dm udev rules,
TBH I am not sure how it works now there.

(On my Debian I have 55-dm.rules which completes that semaphore operation your example is waiting for.)

Milan