kernel not configured for semaphores

[Paolo Galtieri]

Folks,
   twice now in the last 2 days when I have sat in front of my PC I have 
found the following message on the screen:

Kernel not configured for semaphores (System V IPC). Not using udev 
synchronization code.
Halting.

Since I have not modified my kernel from what I downloaded when I did 
the most recent update I don't understand why this message is appearing. 
Both times it occurred during the night because I find it first thing in 
the morning.

Anyone have any idea what is causing this message to appear?

Any help is appreciated.

Thanks,
Paolo

[stan]

On Thu, 10 May 2018 07:57:29 -0700
Paolo Galtieri  wrote:
> Folks,
>    twice now in the last 2 days when I have sat in front of my PC I
> have found the following message on the screen:
>
> Kernel not configured for semaphores (System V IPC). Not using udev 
> synchronization code.
> Halting.
>
> Since I have not modified my kernel from what I downloaded when I did 
> the most recent update I don't understand why this message is
> appearing. Both times it occurred during the night because I find it
> first thing in the morning.
>
> Anyone have any idea what is causing this message to appear?

This is probably something else other than the kernel that has a bug.
You can check if your kernel has semaphores set by going into /boot and
running 
grep -i -e 'IPC' [config file for your running kernel]
It should show something like
CONFIG_SYSVIPC=y
CONFIG_SYSVIPC_SYSCTL=y
CONFIG_IPC_NS=y
My suspicion would fall on systemd as a cause for your problem.  But
that's just a guess based on the error message, I haven't actually
checked for the error message in the source.

[Rick Stevens]

On 05/10/2018 09:00 AM, stan wrote:
> On Thu, 10 May 2018 07:57:29 -0700
> Paolo Galtieri  wrote:
> > Folks,
> >    twice now in the last 2 days when I have sat in front of my PC I
> > have found the following message on the screen:
> >
> > Kernel not configured for semaphores (System V IPC). Not using udev 
> > synchronization code.
> > Halting.
> >
> > Since I have not modified my kernel from what I downloaded when I did 
> > the most recent update I don't understand why this message is
> > appearing. Both times it occurred during the night because I find it
> > first thing in the morning.
> >
> > Anyone have any idea what is causing this message to appear?
>
> This is probably something else other than the kernel that has a bug.
> You can check if your kernel has semaphores set by going into /boot and
> running 
> grep -i -e 'IPC' [config file for your running kernel]

Easier command:

grep -i -e 'IPC' /boot/config-`uname -r`
> It should show something like
> CONFIG_SYSVIPC=y
> CONFIG_SYSVIPC_SYSCTL=y
> CONFIG_IPC_NS=y
> My suspicion would fall on systemd as a cause for your problem.  But
> that's just a guess based on the error message, I haven't actually
> checked for the error message in the source.

On my F28 VM (updating as I write this, but...):

[root@fedora28-vm sysvipc]# uname -r
    4.16.5-300.fc28.x86_64
    [root@fedora28-vm sysvipc]# grep -i -e 'IPC' /boot/config-`uname -r`
    CONFIG_SYSVIPC=y
    CONFIG_SYSVIPC_SYSCTL=y

And:

[root@fedora28-vm sysvipc]# ls -l /proc/sysvipc
    total 0
    -r--r--r--. 1 root root 0 May 10 10:12 msg
    -r--r--r--. 1 root root 0 May 10 10:12 sem
    -r--r--r--. 1 root root 0 May 10 10:12 shm

which indicates that the SYSV IPC stuff IS there.

It'd be odd for a kernel to be built without semaphores as they are a
heavily-used IPC mechanism. Can you please let us know what version of
the kernel you're using? "uname -r" will give it to you (as I showed
above).
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital    [e-mail] -
- AIM/Skype: therps2        ICQ: 22643734            Yahoo: origrps2 -
-                                                                    -
-      If you are what you eat, then I'm fast, cheap and greasy!     -
----------------------------------------------------------------------

[Samuel Sieb]

On 05/10/2018 07:57 AM, Paolo Galtieri wrote:
> Kernel not configured for semaphores (System V IPC). Not using udev 
> synchronization code.
> Halting.
>
> Since I have not modified my kernel from what I downloaded when I did 
> the most recent update I don't understand why this message is appearing. 
> Both times it occurred during the night because I find it first thing in 
> the morning.
>
> Anyone have any idea what is causing this message to appear?

The message is incorrect.  I think I've seen it myself before and I've 
definitely seen various reports about it.  I believe it's an selinux 
issue related to the initramfs in some way.  Did you do any updates 
before rebooting?

[Paolo Galtieri]

This started after installing updates on May 7.  This is my /boot

total 203097
drwx------. 2 root root    12288 Jul 22  2013 lost+found
-rwxr-xr-x. 1 root root  5055896 Jul 22  2013 
vmlinuz-0-rescue-214d3a974ba7461ea2faec5efd479db5
-rw-------. 1 root root 27166889 Jul 22  2013 
initramfs-0-rescue-214d3a974ba7461ea2faec5efd479db5.img
-rw-r--r--. 1 root root   567236 Nov  3  2015 initrd-plymouth.img
drwxr-xr-x. 2 root root     3072 Dec 28 20:38 extlinux
drwxr-xr-x. 3 root root     1024 Jan  8 14:38 efi
-rw-------. 1 root root  3777432 Apr 12 11:36 
System.map-4.15.17-300.fc27.x86_64
-rw-r--r--. 1 root root   194527 Apr 12 11:36 config-4.15.17-300.fc27.x86_64
-rwxr-xr-x. 1 root root  8212664 Apr 12 11:37 
vmlinuz-4.15.17-300.fc27.x86_64
-rw-------. 1 root root  3811910 Apr 19 12:50 
System.map-4.16.3-200.fc27.x86_64
-rw-r--r--. 1 root root   196398 Apr 19 12:50 config-4.16.3-200.fc27.x86_64
-rwxr-xr-x. 1 root root  8282296 Apr 19 12:50 vmlinuz-4.16.3-200.fc27.x86_64
-rw-------. 1 root root 22940500 Apr 22 12:25 
initramfs-4.15.17-300.fc27.x86_64.img
-rw-------. 1 root root  3812235 Apr 24 16:35 
System.map-4.16.4-200.fc27.x86_64
-rw-r--r--. 1 root root   196398 Apr 24 16:35 config-4.16.4-200.fc27.x86_64
-rwxr-xr-x. 1 root root  8286392 Apr 24 16:36 vmlinuz-4.16.4-200.fc27.x86_64
-rw-------. 1 root root 22743125 Apr 27 09:09 
initramfs-4.16.3-200.fc27.x86_64.img
-rw-------. 1 root root  3812494 Apr 27 12:28 
System.map-4.16.5-200.fc27.x86_64
-rw-r--r--. 1 root root   196398 Apr 27 12:28 config-4.16.5-200.fc27.x86_64
-rwxr-xr-x. 1 root root  8286392 Apr 27 12:28 vmlinuz-4.16.5-200.fc27.x86_64
-rw-------. 1 root root 22692787 Apr 30 11:15 
initramfs-4.16.4-200.fc27.x86_64.img
-rw-------. 1 root root 22694199 May  1 09:48 
initramfs-4.16.5-200.fc27.x86_64.img
-rw-------. 1 root root  3812425 May  1 17:58 
System.map-4.16.6-202.fc27.x86_64
-rw-r--r--. 1 root root   196398 May  1 17:59 config-4.16.6-202.fc27.x86_64
-rwxr-xr-x. 1 root root  8282296 May  1 18:01 vmlinuz-4.16.6-202.fc27.x86_64
drwxr-xr-x. 7 root root     1024 May  7 09:52 
214d3a974ba7461ea2faec5efd479db5
-rw-------. 1 root root 22694159 May  7 09:53 
initramfs-4.16.6-202.fc27.x86_64.img
drwx------. 6 root root     1024 May  7 09:53 grub2

Paolo

On 05/10/2018 10:29 AM, Samuel Sieb wrote:
> On 05/10/2018 07:57 AM, Paolo Galtieri wrote:
> > Kernel not configured for semaphores (System V IPC). Not using udev 
> > synchronization code.
> > Halting.
> >
> > Since I have not modified my kernel from what I downloaded when I did 
> > the most recent update I don't understand why this message is 
> > appearing. Both times it occurred during the night because I find it 
> > first thing in the morning.
> >
> > Anyone have any idea what is causing this message to appear?
>
> The message is incorrect.  I think I've seen it myself before and I've 
> definitely seen various reports about it.  I believe it's an selinux 
> issue related to the initramfs in some way.  Did you do any updates 
> before rebooting?
> _______________________________________________
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]

[Paolo Galtieri]

Happened again just a short while ago.  Here's the info from 
/boot/config-4.16.7-200.fc27.x86_64

CONFIG_SYSVIPC=y
CONFIG_SYSVIPC_SYSCTL=y
CONFIG_IPC_NS=y
CONFIG_ARCH_WANT_COMPAT_IPC_PARSE_VERSION=y
CONFIG_ARCH_WANT_OLD_COMPAT_IPC=y
CONFIG_SYSVIPC_COMPAT=y
CONFIG_XFRM_IPCOMP=m
CONFIG_INET_IPCOMP=m
CONFIG_INET6_IPCOMP=m
CONFIG_NETFILTER_XT_MATCH_IPCOMP=m
CONFIG_TIPC=m
# CONFIG_TIPC_MEDIA_IB is not set
CONFIG_TIPC_MEDIA_UDP=y
CONFIG_ISDN_DIVAS_BRIPCI=y
CONFIG_ISDN_DIVAS_PRIPCI=y
CONFIG_PCIPCWATCHDOG=m
CONFIG_DVB_SMIPCIE=m
CONFIG_SND_CMIPCI=m
CONFIG_SND_SST_IPC=m
CONFIG_SND_SST_IPC_PCI=m
CONFIG_SND_SST_IPC_ACPI=m
# CONFIG_INTEL_PMC_IPC is not set
CONFIG_INTEL_PUNIT_IPC=m

Paolo

On 05/10/2018 10:29 AM, Samuel Sieb wrote:
> On 05/10/2018 07:57 AM, Paolo Galtieri wrote:
> > Kernel not configured for semaphores (System V IPC). Not using udev 
> > synchronization code.
> > Halting.
> >
> > Since I have not modified my kernel from what I downloaded when I did 
> > the most recent update I don't understand why this message is 
> > appearing. Both times it occurred during the night because I find it 
> > first thing in the morning.
> >
> > Anyone have any idea what is causing this message to appear?
>
> The message is incorrect.  I think I've seen it myself before and I've 
> definitely seen various reports about it.  I believe it's an selinux 
> issue related to the initramfs in some way.  Did you do any updates 
> before rebooting?
> _______________________________________________
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]