ondemand script background option problem

[Jiri Trnka]

Binary package hint: sysvinit

Ubuntu 10.04 LTS

CPU frequency scaling governor is expected to be automatically set to "ondemand" by /etc/init.d/ondemand script approx. 60s after system boot. Actually, it does not work - it remains set to "performance".

There is a mistake in /etc/init.d/ondemand at line 19 where ondemand script is being run in background mode:

... /etc/init.d/ondemand -- background

should be changed to

... /etc/init.d/ondemand background.

This solves the problem.

ProblemType: Bug
Architecture: i386
Date: Wed May 5 22:05:54 2010
DistroRelease: Ubuntu 8.04
Package: initscripts 2.86.ds1-14.1ubuntu45.1
PackageArchitecture: i386
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: sysvinit
Uname: Linux 2.6.24-27-generic i686

[Jiri Trnka (jiri-trnka-79)]

The bug regards really Ubuntu 10.04 although the automatically added details were taken from 8.04, because I wrote this report on machine with 8.04. Sorry for that confusion.

[Jiri Trnka (jiri-trnka-79)]

This bug and workaround works for my laptop with fresh installation of Lucid. However, in my desktop (which was upgraded from Intrepid to Lucid), everything works fine although I have not removed the mistake from ondemand script... strange ... both systems run the same version and configuration of Ubuntu 10.04 with all updates.

[karlrt (karlrt)]

changing the script saved my problem with lucid too. Hope this gets fixed, as its really easy and annoying to many laptop users (mine is tp t61 btw)

[karlrt (karlrt)]

i just figured out that lucid starts the script only at the end of the bootprocess. My boot takes 35 seconds, at 30 seconds, /etc/init.d/ondemand ist started, with the 60 seconds in the script lucid leaves me 55 seconds in performance for nothing, this is really annoying once on battery power!

[krul (krul)]

I can confirm the bug and resolution of the bug reported.

[karlrt (karlrt)]

I have reinstalled lucid by scratch, and it didnt happen to me the first week, but now i have the problem again. Removing the -- before background seems to solve the issue. Weird that it happened just without changing the system at all (first boot today was okay, second boot stuck at performance-governor!

[FactTech (launchpad-facttechnologies)]

Is there really a bug in /etc/init.d/ondemand? The man page for start-stop-daemon at

http://manpages.ubuntu.com/manpages/lucid/man8/start-stop-daemon.8.html

seems to say that the "--" portion of the command you are referring to is optional (but legal) when using the "--start" parameter.

[tonnzor (tonn81)]

I have the same issue on fresh installation of Ubuntu 10.04. The fix suggested in the initial message solved the issue.

[Steve Langasek (vorlon)]

There is nothing wrong with that line of the init script. Whatever was preventing the 'ondemand' governor from being chosen is unrelated to the use of '-- background'.

So there may be (or may have been) a bug preventing the governor being set, but there's not enough information here to explain why. The ondemand init script has been working fine for the vast majority of users.

[Launchpad Janitor (janitor)]

[Expired for sysvinit (Ubuntu) because there has been no activity for 60 days.]