From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] cryptsetup luksOpen hang on semop
Date: Tue, 9 Jun 2015 07:59:05 +0200 [thread overview]
Message-ID: <20150609055905.GA26186@tansi.org> (raw)
In-Reply-To: <55767B88.8060307@gmail.com>
On Tue, Jun 09, 2015 at 07:37:12 CEST, Milan Broz wrote:
>
> 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
>
FAQ is here:
https://gitlab.com/cryptsetup/cryptsetup/wikis/FrequentlyAskedQuestions/
Mailing List archive is given in FAQ ite, 1.7
Without having time to look at the defaults of your issue, usually
these lockups are causes by the other side having problems (as
Milan explains below). Automagic is nice when it works, but a pain
to debug when it does not.
Note that udev/LVM2 is not part of the cryptsetup project.
Regards,
Arno
> 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
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., Email: arno@wagner.name
GnuPG: ID: CB5D9718 FP: 12D6 C03B 1B30 33BB 13CF B774 E35C 5FA1 CB5D 9718
----
A good decision is based on knowledge and not on numbers. -- Plato
If it's in the news, don't worry about it. The very definition of
"news" is "something that hardly ever happens." -- Bruce Schneier
next prev parent reply other threads:[~2015-06-09 5:59 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
2015-06-09 5:59 ` Arno Wagner [this message]
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=20150609055905.GA26186@tansi.org \
--to=arno@wagner.name \
--cc=dm-crypt@saout.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.