Bug#985150: systemd-udevd is trying read from unused module acpi-cpufreq
On Tue, 2021-03-16 at 22:03 +0100, Michael Biebl wrote: > Am 16.03.21 um 22:01 schrieb Anonimno: > > On Tue, 2021-03-16 at 21:05 +0100, Michael Biebl wrote: > > > Am 16.03.21 um 21:01 schrieb Anonimno: > > > > Attached please find the boot log. > > > > As you can probably see, the error msg is not there directly > > > > after > > > > the > > > > boot. It shows up some time later. Didn't figure out, if there > > > > is a > > > > specific trigger e.g. suspend or similar. > > > > > > Maybe you have laptop-mode-tools or something similar installed. > > > l-m- > > > t > > > is known to do weird stuff. > > > > > > Michael > > > > > > > > > > I have TLP installed. This could be a trigger ... will take a look. > > Now running for an hour or so, without suspend or similar. Nothing > > in > > the logs until now. > > > > Please uninstall tlp and see if that helps > 3 days with multiple suspend, poweroff cycles. The issue did not occur again. Please close the bug! Thank you for your support!
Bug#985150: systemd-udevd is trying read from unused module acpi-cpufreq
On Tue, 2021-03-16 at 21:05 +0100, Michael Biebl wrote: > Am 16.03.21 um 21:01 schrieb Anonimno: > > Attached please find the boot log. > > As you can probably see, the error msg is not there directly after > > the > > boot. It shows up some time later. Didn't figure out, if there is a > > specific trigger e.g. suspend or similar. > > Maybe you have laptop-mode-tools or something similar installed. l-m- > t > is known to do weird stuff. > > Michael > > I have TLP installed. This could be a trigger ... will take a look. Now running for an hour or so, without suspend or similar. Nothing in the logs until now.
Bug#985150: systemd-udevd is trying read from unused module acpi-cpufreq
On Tue, 2021-03-16 at 21:04 +0100, Michael Biebl wrote: > Am 16.03.21 um 21:01 schrieb Anonimno: > > Attached please find the boot log. > > As you can probably see, the error msg is not there directly after > > the > > boot. It shows up some time later. Didn't figure out, if there is a > > specific trigger e.g. suspend or similar. > > Ok, we need a journal log from when the problem shows up. > > I will keep the laptop powered on and have a look every once in a while in the logs. As soon as it pops up, you'll get it :).