View previous topic :: View next topic |
Author |
Message |
Cygon Tux's lil' helper

Joined: 05 Feb 2006 Posts: 115 Location: Germany
|
Posted: Sun Nov 10, 2019 7:49 am Post subject: Kernel uses systemd-udevd on OpenRC after recompile [SOLVED] |
|
|
Hi!
I'm renting a dedicated server onto which I installed Gentoo (sneakily via the hosting provider's recovery console). It's been running fine since 2010 or 2014.
Yesterday, after an emerge --sync, I noticed that GCC 9.2 was marked stable, so I went:
Code: | emerge --update gcc
eselect gcc set 2 # 9.2.0
emerge --oneshot binutils
emerge --oneshot libtool
emerge --oneshot glibc
cd /usr/src/linux
make clean
make
emerge --deep --update --newuse --emptytree @system @world |
Portage compiled all packages successfully. So I installed the new kernel on my boot partition, updated LILO (yeah, still using it) and rebooted.
The server didn't come up again.
From the recovery system (basically same as booting from a live CD for this hosting provider), I can see that the kernel booted (/var/log/dmesg is up-to-date and shows the new kernel version). I switched back to the previous kernel (4.19.27) and tried again... no luck.
Now I'm a bit weirded out by the dmesg I'm seeing:
Code: | [ 0.000000] Linux version 4.19.27-gentoo-r1 (root@orion2521) (gcc version 8.2.0 (Gentoo 8.2.0-r6 p1.7)) #1 SMP Sat Mar 23 17:31:42 CET 2019
[ 0.000000] Command line: auto BOOT_IMAGE=gentoo ro root=903 root=/dev/md3
[ 0.000000] random: get_random_u32 called from bsp_init_amd+0x141/0x290 with crng_init=0
... normal kernel blabbering ...
[ 2.547571] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x2127a77426a, max_idle_ns: 440795248617 ns
[ 2.547683] clocksource: Switched to clocksource tsc
[ 3.306241] systemd-udevd[1557]: /lib64/udev/rules.d/11-dm-lvm.rules:40 Invalid value for OPTIONS key, ignoring: 'event_timeout=180'
[ 3.306245] systemd-udevd[1557]: /lib64/udev/rules.d/11-dm-lvm.rules:40 The line takes no effect, ignoring.
[ 3.356913] systemd-udevd[1557]: /lib64/udev/rules.d/11-dm-lvm.rules:40 Invalid value for OPTIONS key, ignoring: 'event_timeout=180'
[ 3.356918] systemd-udevd[1557]: /lib64/udev/rules.d/11-dm-lvm.rules:40 The line takes no effect, ignoring.
[ 3.418903] systemd-udevd[1612]: Using default interface naming scheme 'v243'.
[ 3.420941] systemd-udevd[1612]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
[ 3.421029] r8169 0000:02:00.0 wan0: renamed from eth0
[ 3.442964] md1:
[ 3.443779] systemd-udevd[1631]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
[ 3.443780] systemd-udevd[1604]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
[ 3.453438] systemd-udevd[1612]: eth0: Process 'net.sh wan0 start' failed with exit code 1.
[ 3.453934] systemd-udevd[1614]: Using default interface naming scheme 'v243'.
[ 3.875134] md1:
[ 3.941053] EXT4-fs (md3): re-mounted. Opts: (null)
[ 3.993200] random: ln: uninitialized urandom read (6 bytes read)
[ 4.041591] Adding 33554428k swap on /dev/sda2. Priority:0 extents:1 across:33554428k SS
[ 4.046119] Adding 33554428k swap on /dev/sdb2. Priority:0 extents:1 across:33554428k SS
[ 4.185072] random: mktemp: uninitialized urandom read (10 bytes read) |
1. What is systemd-udevd? I'm running OpenRC, should that be in my dmesg like that?
2. I've used udev rules to rename my public ethernet interface to wan0. The message 'net.sh wan0 start' leads me to suspect the udev renaming isn't working anymore
Have I accidentally enabled some systemd stuff? eselect profile list shows I'm definitely not on a systemd profile...
Last edited by Cygon on Sun Nov 10, 2019 8:32 am; edited 1 time in total |
|
Back to top |
|
 |
Cygon Tux's lil' helper

Joined: 05 Feb 2006 Posts: 115 Location: Germany
|
Posted: Sun Nov 10, 2019 8:15 am Post subject: |
|
|
Compared it with my workstation, eudev was not installed on the server?!
I could swear I copied the kernel .config file into my kernel source directory and did make olddefconfig weeks ago, but assuming I forgot, could it be that the default .config generated would enable systemd here?
Code: | #
# Support for init systems, system and service managers
#
CONFIG_GENTOO_LINUX_INIT_SCRIPT=y
# CONFIG_GENTOO_LINUX_INIT_SYSTEMD is not set |
Too bad I can't check anymore, I've already copied the .config from the previous kernel over it. |
|
Back to top |
|
 |
Cygon Tux's lil' helper

Joined: 05 Feb 2006 Posts: 115 Location: Germany
|
Posted: Sun Nov 10, 2019 8:31 am Post subject: |
|
|
Okay, after emerging eudev and rebuilding the kernel once again, my server is coming up again.
What could be the reason my system compiled without eudev?
I removed sys-fs/eudev from /var/lib/portage/world by hand and did an emerge --deep --update --newuse world and emerge --depclean, but portage seems to consider eudev to be part of my system now.
Despite the issue being solved, if anyone could think of a reason why my server suddenly switched to systemd-udevd I'd be grateful.
Especially since it seems to not just be a wrong kernel .config, but sys-fs/eudev was missing, too. |
|
Back to top |
|
 |
krinn Watchman


Joined: 02 May 2003 Posts: 7475
|
|
Back to top |
|
 |
Hu Administrator

Joined: 06 Mar 2007 Posts: 23513
|
Posted: Sun Nov 10, 2019 6:08 pm Post subject: |
|
|
Cygon wrote: | Code: | emerge --deep --update --newuse --emptytree @system @world |
| Did Portage tell you in this list that it was switching from eudev to udev? Cygon wrote: | Code: | [ 3.306241] systemd-udevd[1557]: /lib64/udev/rules.d/11-dm-lvm.rules:40 Invalid value for OPTIONS key, ignoring: 'event_timeout=180' | 1. What is systemd-udevd? I'm running OpenRC, should that be in my dmesg like that? | It is the udev provided by sys-fs/udev. It was renamed like that when the systemd project absorbed udev. That absorption is part of why eudev exists. Cygon wrote: | Code: | [ 3.421029] r8169 0000:02:00.0 wan0: renamed from eth0 | 2. I've used udev rules to rename my public ethernet interface to wan0. The message 'net.sh wan0 start' leads me to suspect the udev renaming isn't working anymore | The dmesg output says the rename worked. What did you see that makes you think it did not? Cygon wrote: | Have I accidentally enabled some systemd stuff? eselect profile list shows I'm definitely not on a systemd profile... | You enabled the non-eudev version of udev, probably when you installed it via your full system re-emerge. |
|
Back to top |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|