DM-Crypt Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Steinhuber <sebastian.steinhuber@googlemail.com>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] The weird bug again: semid XXXXXX: semop failed for cookie 0xdeadbeef: incorrect semaphore state
Date: Thu, 03 Nov 2011 16:32:11 +0100	[thread overview]
Message-ID: <j8uc5r$shm$1@dough.gmane.org> (raw)
In-Reply-To: <4E53945D.7060809@redhat.com>

Am 23.08.2011 13:51, schrieb Milan Broz:
> My simple patch was just committed to driver's git, so it will appear shortly
> in linux-next. There is cc to stable so I think it will appear in stable
> update later.
> 
> If anyone want to try it:
> https://lkml.org/lkml/2011/8/22/155
> 
> Thanks,
> Milan

Hi!
It seems that the patch was committed to 2.6.32 and 2.6.33 for now,
according to LKML.
However, I reproduced the behavior with chromium and google-chrome.
Maybe the patch was not commited to mainline:

"semid 688130: semop failed for cookie 0xd4d5abf: incorrect semaphore state
Failed to set a proper state for notification semaphore identified by
cookie value 223173311 (0xd4d5abf) to initialize waiting for incoming
notifications."

I'm running debian unstable with a customized vanilla kernel 3.0.7 with
vserver patch, cryptsetup 1.3.0, udev 172, chromium 14.0, google-chrome
15.0.

Best,
Sebastian

  parent reply	other threads:[~2011-11-03 15:35 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
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 [this message]
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='j8uc5r$shm$1@dough.gmane.org' \
    --to=sebastian.steinhuber@googlemail.com \
    --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