From: Alexander Koch <mail@alexanderkoch.net>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] The weird bug again: semid XXXXXX: semop failed for cookie 0xdeadbeef: incorrect semaphore state
Date: Wed, 17 Aug 2011 13:22:23 +0200 [thread overview]
Message-ID: <4E4BA46F.5010809@alexanderkoch.net> (raw)
In-Reply-To: <4E4B6E61.4020301@redhat.com>
> What says "ipcs -s" (with and without chromium running)?
I get an empty list, no matter if chromium is running or not:
[alex@thor ~]$ LC_ALL=C ipcs -s
------ Semaphore Arrays --------
key semid owner perms nsems
> Will increasing number of system semaphores help (first number)?
> sysctl -a |grep sem
Default was 250, increasing to 1000 had no effect:
[alex@thor ~]$ sudo vgchange -an ArchiveGroup
0 logical volume(s) in volume group "ArchiveGroup" now active
semid 557056: semop failed for cookie 0xd4d88de: incorrect semaphore
state
Failed to set a proper state for notification semaphore identified
by cookie value 223185118 (0xd4d88de) to initialize waiting for incoming
notifications.
Besides, I got this message in the logs, don't know if this could be
related:
chromium-sandbo (2120): /proc/2118/oom_adj is deprecated, please use
/proc/2118/oom_score_adj instead.
Greetings
Alex
next prev parent reply other threads:[~2011-08-17 9:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-16 20:45 [dm-crypt] The weird bug again: semid XXXXXX: semop failed for cookie 0xdeadbeef: incorrect semaphore state Thomas Bächler
2011-08-16 21:44 ` Milan Broz
2011-08-16 21:55 ` Thomas Bächler
2011-08-17 7:31 ` Milan Broz
2011-08-17 11:22 ` Alexander Koch [this message]
2011-08-17 10:43 ` Yves-Alexis Perez
2011-08-17 10:48 ` Milan Broz
2011-08-17 11:30 ` Milan Broz
2011-08-17 12:17 ` Yves-Alexis Perez
2011-08-18 8:56 ` Milan Broz
2011-08-18 9:56 ` Thomas Bächler
2011-08-18 10:25 ` Milan Broz
2011-08-22 11:51 ` Thomas Bächler
2011-08-23 10:01 ` Thomas Bächler
2011-08-23 11:51 ` Milan Broz
2011-09-16 6:33 ` Thomas Bächler
2011-11-03 15:32 ` Sebastian Steinhuber
2011-11-10 11:28 ` Milan Broz
2011-08-18 20:49 ` Yves-Alexis Perez
2011-08-16 22:12 ` Alexander Koch
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=4E4BA46F.5010809@alexanderkoch.net \
--to=mail@alexanderkoch.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox