After booting to uname -r 3.19.4-1.g74c332b-xen Boot log fails include dmesg | grep -i modules [ 0.144000] Modules linked in: [ 4.357642] systemd[1]: Failed to start Load Kernel Modules. [ 25.284199] systemd-modules-load[779]: Inserted module 'pciback' [ 35.284122] systemd-modules-load[779]: Failed to find module 'xen-acpi-processor' [ 45.312110] systemd-modules-load[779]: Inserted module 'blktap2' [ 47.972022] systemd[1]: Failed to start Load Kernel Modules. Systemd's service fails systemctl status systemd-modules-load.service systemd-modules-load.service - Load Kernel Modules Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static) Active: failed (Result: exit-code) since Sat 2015-04-18 14:59:05 PDT; 27min ago Docs: man:systemd-modules-load.service(8) man:modules-load.d(5) Process: 779 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE) Main PID: 779 (code=exited, status=1/FAILURE) The module exists locate xen | grep acpi | grep proc | grep 3.19.4 /lib/modules/3.19.4-1.g74c332b-xen/kernel/drivers/acpi/processor.ko is not loaded after boot lsmod | grep acpi acpi_pad 12960 0 Can't be loaded by the given name modprobe xen-acpi-processor modprobe: FATAL: Module xen-acpi-processor not found. And isn't mentioned (as CONFIG_XEN_ACPI_PROCESSOR) in the kernel config grep PROCESSOR /boot/config-3.19.4-1.g74c332b-xen # CONFIG_PROCESSOR_SELECT is not set CONFIG_ACPI_PROCESSOR=m CONFIG_ACPI_PROCESSOR_AGGREGATOR=m CONFIG_PROCESSOR_EXTERNAL_CONTROL=y On this server xenpm get-cpufreq-states cpu id : 0 total P-states : 16 usable P-states : 16 current frequency : 800 MHz P0 [3101 MHz]: transition [ 314] residency [ 13730 ms] P1 [3100 MHz]: transition [ 4] residency [ 23 ms] P2 [2900 MHz]: transition [ 2] residency [ 21 ms] P3 [2800 MHz]: transition [ 7] residency [ 33 ms] P4 [2600 MHz]: transition [ 5] residency [ 4 ms] P5 [2400 MHz]: transition [ 4] residency [ 0 ms] P6 [2300 MHz]: transition [ 3] residency [ 21 ms] P7 [2100 MHz]: transition [ 8] residency [ 30 ms] P8 [1900 MHz]: transition [ 5] residency [ 2 ms] P9 [1800 MHz]: transition [ 12] residency [ 56 ms] P10 [1600 MHz]: transition [ 5] residency [ 13 ms] P11 [1500 MHz]: transition [ 7] residency [ 39 ms] P12 [1300 MHz]: transition [ 8] residency [ 34 ms] P13 [1100 MHz]: transition [ 5] residency [ 33 ms] P14 [1000 MHz]: transition [ 20] residency [ 123 ms] *P15 [ 800 MHz]: transition [ 296] residency [ 6896 ms] xenpm get-cpufreq-para cpu id : 0 affected_cpus : 0 cpuinfo frequency : max [3101000] min [800000] cur [3100000] scaling_driver : acpi-cpufreq scaling_avail_gov : userspace performance powersave ondemand current_governor : ondemand ondemand specific : sampling_rate : max [10000000] min [10000] cur [20000] up_threshold : 80 scaling_avail_freq : 3101000 3100000 2900000 2800000 2600000 2400000 2300000 2100000 1900000 1800000 1600000 1500000 1300000 1100000 1000000 *800000 scaling frequency : max [3101000] min [800000] cur [800000] turbo mode : enabled [CPU1] failed to get cpufreq parameter [CPU2] failed to get cpufreq parameter [CPU3] failed to get cpufreq parameter I want to fix, or avoid, the on-boot systemd failure. Is this a bug, or a config fix? LT -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org