From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gmazyland@gmail.com>
Received: from mail-wg0-x244.google.com (mail-wg0-x244.google.com
 [IPv6:2a00:1450:400c:c00::244])
 (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>; Tue,  9 Jun 2015 07:37:16 +0200 (CEST)
Received: by wggx12 with SMTP id x12so1329117wgg.1
 for <dm-crypt@saout.de>; Mon, 08 Jun 2015 22:37:15 -0700 (PDT)
Message-ID: <55767B88.8060307@gmail.com>
Date: Tue, 09 Jun 2015 07:37:12 +0200
From: Milan Broz <gmazyland@gmail.com>
MIME-Version: 1.0
References: <1886950740.9229159.1433812510357.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: <1886950740.9229159.1433812510357.JavaMail.yahoo@mail.yahoo.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Subject: Re: [dm-crypt] cryptsetup  luksOpen  hang on semop
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: laxmikanth reddy <plkreddy2000@yahoo.com>, "dm-crypt@saout.de" <dm-crypt@saout.de>


On 06/09/2015 03:15 AM, laxmikanth reddy wrote:
> Hi Team,
> Wee are working embedded system bringup with custom build kernel 3.10.65 version.
> and kernel version is 3.10.65.
> Here, we are trying to mount the encrypted disk, when udev rule match the uevent,
> with "cryptsetup luksOpen ..", and it is getting hang at semop. cryptsetup 1.6.1.
> Can you please share light on, what could be the possible reasons for this issue?
> Appriciate your help and any pointers, to debug this issue. Thanks in advance.

Maybe you should start with reading FAQ and archive, similar problem was here
just few weeks ago, please read this thread
http://article.gmane.org/gmane.linux.kernel.device-mapper.dm-crypt/8049

I think your system is just compiled with udev support but missing mandatory
device mapper udev rules (libdevmapper library and udev rules are part of lvm2 package,
cryptsetup depends on it).

Also please use new version (1.6.7) there were some bugfixes, 1.6.1 is pretty old version.

> Foloowing is the starce log, for "cryptsetup luksOpen ..":
> 
> bash-4.2# strace /sbin/cryptsetup --debug --batch-mode luksOpen /dev/bootdisk2>
> execve("/sbin/cryptsetup", ["/sbin/cryptsetup", "--debug", "--batch-mode", "luksOpen", "/dev/bootdisk2", "NVRAM", "--key-file", "/varied/nv_bb"], [/* 12 vars */]) = 0

Please better always paste --debug log (which is sanitized), we need strace only
if requested (see FAQ).

Milan