From: Udo van den Heuvel <udovdh@xs4all.nl>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: 3.8.5: incorrect semaphore state issue
Date: Sat, 13 Apr 2013 13:27:06 +0200 [thread overview]
Message-ID: <5169410A.8050602@xs4all.nl> (raw)
Hello,
This morning I did a luksOpen on an external harddisk and saw:
# cryptsetup luksOpen /dev/sde1 crypto2
Enter passphrase for /dev/sde1:
semid 557063: semop failed for cookie 0xd4dd6db: incorrect semaphore state
Failed to set a proper state for notification semaphore identified by
cookie value 223205083 (0xd4dd6db) to initialize waiting for incoming
notifications.
# mount /dev/mapper/crypto2 /media
#
So stuff worked OK, just the unexpected messages.
I did find an ubuntu bug from 2011 so what needs fixing this time?
Please advise!
Kind regards,
Udo
reply other threads:[~2013-04-13 11:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5169410A.8050602@xs4all.nl \
--to=udovdh@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®