From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <corsac@debian.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 bhDWsGmKafpg for <dm-crypt@saout.de>;
 Wed, 17 Aug 2011 12:43:27 +0200 (CEST)
Received: from smtp3-g21.free.fr (smtp3-g21.free.fr [212.27.42.3])
 by mail.saout.de (Postfix) with ESMTP
 for <dm-crypt@saout.de>; Wed, 17 Aug 2011 12:43:26 +0200 (CEST)
Received: from molly.corsac.net (unknown [78.192.68.46])
 by smtp3-g21.free.fr (Postfix) with ESMTP id EF140A6252
 for <dm-crypt@saout.de>; Wed, 17 Aug 2011 12:43:20 +0200 (CEST)
Received: from [192.168.24.20] (plateformev6-124-46.pck.nerim.net
 [62.212.124.46])
 by molly.corsac.net (Postfix) with ESMTPSA id EC3B682CB1
 for <dm-crypt@saout.de>; Wed, 17 Aug 2011 12:43:00 +0200 (CEST)
From: Yves-Alexis Perez <corsac@debian.org>
In-Reply-To: <4E4BA46F.5010809@alexanderkoch.net>
References: <4E4AD6F2.8020800@archlinux.org> <4E4AE4DB.30205@redhat.com>
 <4E4AE740.9020800@archlinux.org> <4E4B6E61.4020301@redhat.com>
 <4E4BA46F.5010809@alexanderkoch.net>
Content-Type: text/plain; charset="UTF-8"
Date: Wed, 17 Aug 2011 12:43:14 +0200
Message-ID: <1313577794.6534.12.camel@oban>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
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

On mer., 2011-08-17 at 13:22 +0200, Alexander Koch wrote:
>   [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. 

vchange is only LVM, not dm-crypt, is it? So might not be related at all
to dm-crypt or cryptsetup?

For chromium, it might be that the default sandboxing (setuid one) uses
PID and network namespaces. Not sure why it'd mess with semaphores, but
maybe there's something to look at there.

Regards,
-- 
Yves-Alexis