All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Thomas Bächler" <thomas@archlinux.org>
To: dm-crypt <dm-crypt@saout.de>
Subject: [dm-crypt] The weird bug again: semid XXXXXX: semop failed for cookie 0xdeadbeef: incorrect semaphore state
Date: Tue, 16 Aug 2011 22:45:38 +0200	[thread overview]
Message-ID: <4E4AD6F2.8020800@archlinux.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 739 bytes --]

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 cannot see any connection here, but it has been confirmed by several
users of different distributions (several Arch users, at least one
Slackware user).

For details, please read: https://bugs.archlinux.org/task/24614

I hope anyone can help.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

             reply	other threads:[~2011-08-16 20:51 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-16 20:45 Thomas Bächler [this message]
2011-08-16 21:44 ` [dm-crypt] The weird bug again: semid XXXXXX: semop failed for cookie 0xdeadbeef: incorrect semaphore state Milan Broz
2011-08-16 21:55   ` Thomas Bächler
2011-08-17  7:31     ` Milan Broz
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=4E4AD6F2.8020800@archlinux.org \
    --to=thomas@archlinux.org \
    --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.