Possibly related to https://code.google.com/p/chromium/issues/detail?id=92762 ?
And from there, a link to https://lkml.org/lkml/2011/8/18/112
Apparently something might have been fixed in the kernel from v3.1 and I see
Precise is using v3.2 which could explain it.
** Bug watch added:
+1 (not experiencing in precise with the newer kernel)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/719388
Title:
semop failed for cookie 0xd4d09ef: incorrect semaphore state during
luksOpen
To
Thanks all, marking as fixed.
** Changed in: cryptsetup (Ubuntu)
Status: Incomplete = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/719388
Title:
semop failed for cookie
This should be fixed in the new version on Precise.
Could somebody test this if their still able to reproduce this?
** Changed in: cryptsetup (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I haven't seen this on Precise.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/719388
Title:
semop failed for cookie 0xd4d09ef: incorrect semaphore state during
luksOpen
To manage notifications
Still happening here.
** Changed in: cryptsetup (Ubuntu)
Status: Fix Released = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/719388
Title:
semop failed for cookie 0xd4d09ef:
I am geting semaphore errors, too.
Setup:
- internal disk SATA
- external disk eSATA
- GPT - LVM - LUKS (cryptsetup)
When creating logical volumes, I get:
The link /dev/ext0/exttest2 should had been created by udev but it was not
found. Falling back to direct link creation.
When removing
I get this error now also. Using Linux netbook 2.6.38-10-generic
#46-Ubuntu SMP Tue Jun 28 15:07:17 UTC 2011 x86_64 x86_64 x86_64
GNU/Linux
semid 688129: semop failed for cookie 0xd4d6c1f: incorrect semaphore state
Failed to set a proper state for notification semaphore identified by cookie
I got this when executing:
zeratul@antioch:~$ sudo cryptsetup luksOpen /dev/md0 raid
Enter passphrase for /dev/md0:
semid 5111810: semop failed for cookie 0xd4dca3f: incorrect semaphore state
Failed to set a proper state for notification semaphore identified by cookie
value 223201855
I get the same semop failed for cookie 0xd4daad3: incorrect semaphore state
errors when removing an LVM volume:
root@mf:~# lvremove /dev/mf/lvmtest3
Do you really want to remove active logical volume lvmtest3? [y/n]: y
semid 393216: semop failed for cookie 0xd4daad3: incorrect semaphore state
I'm seeing these semaphore errors with a backup-script that uses lvm2
snapshots after upgrading to natty.
I think this bug should be reopened and moved to the proper package
(lvm2?) and it should probably be merged with bug #753541
May 9 21:21:43 sphere udevd-work[5144]: inotify_add_watch(6,
Doesn't seem to be an issue anymore with the newest (2.6.38-9-generic)
kernel.
** Changed in: cryptsetup (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Can someone else confirm?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/719388
Title:
semop failed for cookie 0xd4d09ef: incorrect semaphore state during
luksOpen
--
ubuntu-bugs mailing list
I am not sure if anyone from Ubuntu will even respond here, but I
checked upstream code and provided logs (btw thanks for them, very
usefull here).
What happens here is:
- system is fully udev managed, both userspace and kernel are recent enough
- according to logs, something during udev event
I agree, it's non-critical. Thanks for taking the time to further
investigate!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/719388
Title:
semop failed for cookie 0xd4d09ef: incorrect semaphore
Same behavior on luksClose:
9996 17:01:33 ioctl(3, DM_TABLE_STATUS, 0x24d6b30) = 0
9996 17:01:33 open(/dev/urandom, O_RDONLY) = 4
9996 17:01:33 read(4, \254\231, 2) = 2
9996 17:01:33 semget(0xd4d99ac, 1, IPC_CREAT|IPC_EXCL|0600) = 557059
9996 17:01:33 semctl(557059, 0, SETVAL, 0x1) = 0
LuksClose debug attached.
** Attachment added: luksdebug.txt
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/719388/+attachment/2097400/+files/luksdebug.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Looks like the semaphore gets decremented twice.
** Attachment added: semops.txt
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/719388/+attachment/2097423/+files/semops.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
The dm (LVM2) calls
** Attachment added: dm_calls.txt
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/719388/+attachment/2098094/+files/dm_calls.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I can reproduce this too.
** Changed in: cryptsetup (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/719388
Title:
semop failed for cookie 0xd4d09ef: incorrect
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/719388
Title:
semop failed for cookie 0xd4d09ef: incorrect semaphore state during
luksOpen
--
ubuntu-bugs mailing list
21 matches
Mail list logo
