From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <glkdd-dm-crypt@m.gmane.org>
Received: from mail.saout.de ([127.0.0.1])
 by localhost (mail.saout.de [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id pjweuAdcxVUO for <dm-crypt@saout.de>;
 Thu,  3 Nov 2011 16:35:14 +0100 (CET)
Received: from lo.gmane.org (lo.gmane.org [80.91.229.12])
 by mail.saout.de (Postfix) with ESMTP
 for <dm-crypt@saout.de>; Thu,  3 Nov 2011 16:35:13 +0100 (CET)
Received: from list by lo.gmane.org with local (Exim 4.69)
 (envelope-from <glkdd-dm-crypt@m.gmane.org>) id 1RLzJv-0004tf-Ac
 for dm-crypt@saout.de; Thu, 03 Nov 2011 16:35:11 +0100
Received: from p5491d6f5.dip.t-dialin.net ([84.145.214.245])
 by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
 id 1AlnuQ-0007hv-00
 for <dm-crypt@saout.de>; Thu, 03 Nov 2011 16:35:11 +0100
Received: from sebastian.steinhuber by p5491d6f5.dip.t-dialin.net with local
 (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00
 for <dm-crypt@saout.de>; Thu, 03 Nov 2011 16:35:11 +0100
From: Sebastian Steinhuber <sebastian.steinhuber@googlemail.com>
Date: Thu, 03 Nov 2011 16:32:11 +0100
Message-ID: <j8uc5r$shm$1@dough.gmane.org>
References: <4E4AD6F2.8020800@archlinux.org> <4E4AE4DB.30205@redhat.com>
 <4E4AE740.9020800@archlinux.org> <4E4B6E61.4020301@redhat.com>
 <4E4BA46F.5010809@alexanderkoch.net> <1313577794.6534.12.camel@oban>
 <4E4B9C78.70504@redhat.com> <4E4BA673.9060000@redhat.com>
 <1313583460.6534.14.camel@oban> <4E4CD3CF.5050803@redhat.com>
 <4E4CE1B4.2070401@archlinux.org> <4E4CE8AB.9050106@redhat.com>
 <4E5242CE.2010108@archlinux.org> <4E537A8D.8020707@archlinux.org>
 <4E53945D.7060809@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
In-Reply-To: <4E53945D.7060809@redhat.com>
Subject: Re: [dm-crypt] The weird bug again: semid XXXXXX: semop failed for
 cookie 0xdeadbeef: incorrect semaphore state
List-Id: <dm-crypt.saout.de>
List-Unsubscribe: <http://www.saout.de/mailman/options/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=unsubscribe>
List-Archive: <http://www.saout.de/pipermail/dm-crypt>
List-Post: <mailto:dm-crypt@saout.de>
List-Help: <mailto:dm-crypt-request@saout.de?subject=help>
List-Subscribe: <http://www.saout.de/mailman/listinfo/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=subscribe>
To: dm-crypt@saout.de

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