From: Milan Broz <mbroz@redhat.com>
To: "Thomas Bächler" <thomas@archlinux.org>
Cc: dm-crypt <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 09:31:45 +0200 [thread overview]
Message-ID: <4E4B6E61.4020301@redhat.com> (raw)
In-Reply-To: <4E4AE740.9020800@archlinux.org>
On 08/16/2011 11:55 PM, Thomas Bächler wrote:
> Am 16.08.2011 23:44, schrieb Milan Broz:
>> On 08/16/2011 10:45 PM, Thomas Bächler wrote:
>>> I am getting reports of this error again:
>>>
>>> semid 491524: semop failed for cookie 0xd4dc159: incorrect semaphore state
>>> Failed to set a proper state for notification semaphore identified by
>>> cookie value 223199577 (0xd4dc159) to initialize waiting for incoming
>>> notifications.
>>>
>>> This issue is so weird that I don't know where to start. Apparently,
>>> this problem appears whenever chromium is running, and disappears when
>>> you quit chromium. I'm confused about this. Very confused.
>>
>> I know that this bug is still there. I think that the problem is:
>>
>> - kernel, in response to devmapper library request, send uevent with cookie
>> - kernel reports failure (despite uevent was sent), I guess it is
>> some memory allocation error later
>> - libdevmapper takes error path, destroying semaphore, which was already
>> destroyed in udev rules
>>
>> So my guess is that connection with chromium just it perhaps allocates most
>> of system memory and some allocation in kernel perhaps fail then.
>
> Then this would probably be reproducible with other programs, too. So
> far, the connection has been only made with chromium. I would love to
> find another test case though.
Well, this is the most strange report so far. If more people can reproduce it,
there must be a connection. Isn't chromium using system semaphores intensively?
(I have no idea.)
What says "ipcs -s" (with and without chromium running)?
Will increasing number of system semaphores help (first number)?
sysctl -a |grep sem
Can you try to increase it to 1000 for example
sysctl -w kernel.sem=1000
>
>> The final state should be correct, so you can (I hope) ignore that error
>> for now.
>
> Don't the LUKS commands abort after this error? (Don't remember).
It should not.
Milan
next prev parent reply other threads:[~2011-08-17 7:31 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 [this message]
2011-08-17 11:22 ` Alexander Koch
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=4E4B6E61.4020301@redhat.com \
--to=mbroz@redhat.com \
--cc=dm-crypt@saout.de \
--cc=thomas@archlinux.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