Bug#985150: systemd-udevd[…]: could not read from '/sys/module/acpi_cpufreq/initstate': No such device

[Al Ma]

Another user here with the same old bug on a different machine (stationary WS C422 PRO SE with Intel(R) Xeon(R) W-2235 CPU @ 3.80GHz). The journal log entries just before the offending one:
Apr 23 00:34:25 AnonymousMachineName systemd-udevd[397]: Using default interface naming scheme 'v247'.
Apr 23 00:34:25 AnonymousMachineName systemd-udevd[397]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Apr 23 00:34:25 AnonymousMachineName kernel: iwlwifi 0000:b3:00.0 wlp179s0: renamed from wlan0
Apr 23 00:34:25 AnonymousMachineName systemd[1]: Condition check resulted in Dispatch Password Requests to Console Directory Watch being skipped.
Apr 23 00:34:25 AnonymousMachineName systemd[1]: Condition check resulted in File System Check on Root Device being skipped.
Apr 23 00:34:25 AnonymousMachineName systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped.
Apr 23 00:34:25 AnonymousMachineName systemd[1]: Condition check resulted in Platform Persistent Storage Archival being skipped.
Apr 23 00:34:25 AnonymousMachineName kernel: EDAC MC0: Giving out device to module skx_edac controller Skylake Socket#0 IMC#0: DEV 0000:64:0a.0 (INTERRUPT)
Apr 23 00:34:25 AnonymousMachineName kernel: EDAC MC1: Giving out device to module skx_edac controller Skylake Socket#0 IMC#1: DEV 0000:64:0c.0 (INTERRUPT)
Apr 23 00:34:25 AnonymousMachineName systemd-udevd[406]: Using default interface naming scheme 'v247'.
Apr 23 00:34:25 AnonymousMachineName systemd-udevd[406]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Apr 23 00:34:25 AnonymousMachineName systemd-udevd[410]: could not read from '/sys/module/acpi_cpufreq/initstate': No such device
Indeed, the file and even the containing directory is absent:
$ ls /sys/module/acpi_cpufreq
ls: Zugriff auf '/sys/module/acpi_cpufreq' nicht möglich: Datei oder Verzeichnis nicht gefunden
My nondefault lines in /etc/tlp.conf:
$ egrep -v "(^$)|(^#)" /etc/tlp.conf
CPU_SCALING_GOVERNOR_ON_AC=powersave
CPU_SCALING_GOVERNOR_ON_BAT=powersave
CPU_SCALING_MAX_FREQ_ON_AC=1200000
CPU_SCALING_MAX_FREQ_ON_BAT=1200000
DISK_SPINDOWN_TIMEOUT_ON_AC="0 241"
DISK_SPINDOWN_TIMEOUT_ON_BAT="0 241"
SATA_LINKPWR_ON_AC="med_power_with_dipm medium_power"
SATA_LINKPWR_ON_BAT="med_power_with_dipm min_power"
Still, either tlp or sysfsutils do their frequency-setting job satisfactorily:
$ cat /proc/cpuinfo | grep MHz
cpu MHz : 1201.105
cpu MHz : 1200.942
cpu MHz : 1200.752
cpu MHz : 1200.079
cpu MHz : 1199.669
cpu MHz : 1199.822
cpu MHz : 1200.053
cpu MHz : 1200.007
cpu MHz : 1200.144
cpu MHz : 1200.040
cpu MHz : 1199.999
cpu MHz : 1200.186
I don't wish to uninstall tlp (my version: 1.4.0-1) because otherwise the machine might run too hot for its fully passive cooling. I have no idea whether the bug is tlp-related; please feel free to reassing or retag this report if necessary. The bug might be plymouth-related though, because the offending message disappeared when I updated a few packages to their versions from snapshots, among them plymouth from 0.9.5 to 0.9.5+git20211018-1.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20230423/3b09572f/attachment.htm>