device-mapper und Google Chrome

Wednesday, October 26. 2011

Ein seltsamer Effekt ist neuerdings aufgefallen, beim Einbinden der dm-crypt - devices liest sich das so:

cryptsetup luksOpen /dev/sdc silva
Geben Sie den Passsatz für /dev/sdc ein: 
semid 131072: semop failed for cookie 0xd4df6e3: incorrect semaphore state
Failed to set a proper state for notification semaphore identified by cookie value 223213283 (0xd4df6e3) to initialize waiting for incoming notifications.

Und das ist wohl ein Kernel-Bug, der nur sichtbar wird, wenn Google Chrome läuft während man die Dinge einbindet. 


Trackback specific URI for this entry
    No Trackbacks


    No comments

Add Comment

Enclosing asterisks marks text as bold (*word*), underscore are made via _word_.
Standard emoticons like :-) and ;-) are converted to images.
E-Mail addresses will not be displayed and will only be used for E-Mail notifications.

To prevent automated Bots from commentspamming, please enter the string you see in the image below in the appropriate input box. Your comment will only be submitted if the strings match. Please ensure that your browser supports and accepts cookies, or your comment cannot be verified correctly.