From: Milan Broz <gmazyland@gmail.com>
To: laxmikanth reddy <plkreddy2000@yahoo.com>,
"dm-crypt@saout.de" <dm-crypt@saout.de>
Subject: Re: [dm-crypt] cryptsetup luksOpen hang on semop
Date: Tue, 09 Jun 2015 07:37:12 +0200 [thread overview]
Message-ID: <55767B88.8060307@gmail.com> (raw)
In-Reply-To: <1886950740.9229159.1433812510357.JavaMail.yahoo@mail.yahoo.com>
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
next prev parent reply other threads:[~2015-06-09 5:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-09 1:15 [dm-crypt] cryptsetup luksOpen hang on semop laxmikanth reddy
2015-06-09 5:37 ` Milan Broz [this message]
2015-06-09 5:59 ` Arno Wagner
2015-06-15 2:22 ` laxmikanth reddy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55767B88.8060307@gmail.com \
--to=gmazyland@gmail.com \
--cc=dm-crypt@saout.de \
--cc=plkreddy2000@yahoo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox