[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: The weird bug again: semid XXXXXX: semop failed for cookie 0xdeadbeef: incorrect semaphore state



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

_______________________________________________
dm-crypt mailing list
dm-crypt@xxxxxxxx
http://www.saout.de/mailman/listinfo/dm-crypt


[DM Devel]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Packaging]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

Add to Google Powered by Linux