[Bug 740127] Re: ondemand script in initscripts uses arbitrary sleep

Launchpad Bug Tracker 740127 at bugs.launchpad.net
Fri Nov 15 23:19:10 UTC 2013


Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: sysvinit (Ubuntu)
       Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to sysvinit in Ubuntu.
https://bugs.launchpad.net/bugs/740127

Title:
  ondemand script in initscripts uses arbitrary sleep

Status in “sysvinit” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: initscripts

  The ondemand script in the initscripts package is all very well, but
  the 60 second pause before activation is both arbitrary, and in my
  case, wrong.

  The comment next to it suggests that the 60 seconds is to allow the
  desktop to be logged in before the CPU govener is changed.  however my
  laptop gets from grub to desktop in 17 seconds and then I have to wait
  up to one minute from then for my CPUs to be put into ondemand mode.
  Given I can have CPU frequency panel applets which can change the
  frequency govener; why is the ondemand setting not an XDG autostart
  app which uses the same communications channels to set the govener
  after the desktop has started?

  It took me quite some time to track down that this was the issue as I
  was, from a user point of view, simply seeing that my CPU govener
  choice of ondemand was not being preserved across reboots, yet if I
  left my laptop alone for a bit after booting, the CPUs "suddenly" went
  into ondemand mode.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/740127/+subscriptions



More information about the foundations-bugs mailing list