severity 583663 important tags 583663 - patch On Sat, May 29, 2010 at 01:18:09PM +0200, Francesco Poli (t1000) wrote: > Package: cpufreqd > Version: 2.4.2-1 > Severity: important > Tags: patch > User: initscripts-ng-de...@lists.alioth.debian.org > Usertags: incorrect-dependencies > > > Hi Mattia! :) > > Since the parallellized boot was enabled, cpufreqd has no longer been > automatically started during boot. > > The error message is: > > startpar:servce(s) returned failure: cpufreqd failure! > > If I manually issue the following command, after the boot completed: > > # /etc/init.d/cpufreqd start > > the daemon is correctly started and no further problems seem to occur. > > > I am under the impression that this bug is due to incomplete LSB header > dependencies: the attached patch seems to fix the issue.
I don't think that is correct. cpufreqd.init has its own code to load cpu and governor modules. Please find why that is failing instead. You can add `set -x` in the script and inside the `load_cpu_module` and `load_governor_modules` functions, that should tell us what is happening. Also, loadcpufreq is provided by cpufrequtils so if nothing else you forgot to add the proper dependency header to the package. On Sat, May 29, 2010 at 10:11:30PM +0200, Petter Reinholdtsen wrote: > severity 583663 seriuos > thanks > > The patch seem correct, assuming cpufreqd should start after the > kernel modules for cpufreq handling are loaded. > > Assuming this affect all users with the new default setup in Debian > (parallel booting), I am raising the severity to serious. as explained this shouldn't be the case, bringing it back to important. Thanks -- mattia :wq! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
