Change default cpufreq governor to "ondemand"

Bug #626390 reported by Björn Schließmann
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

My Thinkpad T41, with present kernel config (cpufreq default scaling governor "performance"), noticeably heats up on every boot until booting is completely done and /etc/init.d/ondemand changes the governor to "ondemand".

IMHO, default governor "ondemand" would suffice and use high power only when needed (not all the time, because booting heavily depends on hard disk I/O). Please set CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-19-generic 2.6.35-19.26
Regression: No
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.35-19.26-generic 2.6.35.3
Uname: Linux 2.6.35-19-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: chronoss 2040 F.... pulseaudio
 /dev/snd/pcmC0D0p: chronoss 2040 F...m pulseaudio
CRDA:
 country DE:
  (2400 - 2483 @ 40), (N/A, 20)
  (5150 - 5250 @ 40), (N/A, 20), NO-OUTDOOR
  (5250 - 5350 @ 40), (N/A, 20), NO-OUTDOOR, DFS
  (5470 - 5725 @ 40), (N/A, 26), NO-OUTDOOR, DFS
Card0.Amixer.info:
 Card hw:0 'I82801DBICH4'/'Intel 82801DB-ICH4 with AD1981B at irq 5'
   Mixer name : 'Analog Devices AD1981B'
   Components : 'AC97a:41445374'
   Controls : 26
   Simple ctrls : 18
Card29.Amixer.info:
 Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 1RHT71WW-3.04'
   Mixer name : 'ThinkPad EC 1RHT71WW-3.04'
   Components : ''
   Controls : 2
   Simple ctrls : 1
Card29.Amixer.values:
 Simple mixer control 'Console',0
   Capabilities: pvolume pvolume-joined pswitch pswitch-joined penum
   Playback channels: Mono
   Limits: Playback 0 - 14
   Mono: Playback 3 [21%] [off]
Date: Sun Aug 29 20:04:25 2010
HibernationDevice: RESUME=UUID=ba5e9423-6d83-46d6-9a22-0b33ef96ebe3
Lsusb:
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: IBM 2373A91
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-19-generic root=UUID=4d015652-6ae1-4e87-acc6-e8c43a344ba5 ro
ProcEnviron:
 LANGUAGE=en_GB:en_US:en
 PATH=(custom, no user)
 LANG=en_GB.utf8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.38
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UserAsoundrc:
 # ALSA library configuration file

 # Include settings that are under the control of asoundconf(1).
 # (To disable these settings, comment out this line.)
 </home/chronoss/.asoundrc.asoundconf>
WpaSupplicantLog:

dmi.bios.date: 06/18/2007
dmi.bios.vendor: IBM
dmi.bios.version: 1RETDRWW (3.23 )
dmi.board.name: 2373A91
dmi.board.vendor: IBM
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: IBM
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnIBM:bvr1RETDRWW(3.23):bd06/18/2007:svnIBM:pn2373A91:pvrThinkPadT41:rvnIBM:rn2373A91:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
dmi.product.name: 2373A91
dmi.product.version: ThinkPad T41
dmi.sys.vendor: IBM

Revision history for this message
Björn Schließmann (b-schliessmann) wrote :
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi Björn,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Björn Schließmann (b-schliessmann) wrote :

Well, this bug concerns a trivial part of kernel configuration, so I'm not sure what you want me to test.

But I can assure you (just checked), latest upstream git revision b30a3f6 has CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND in its default configuration, though it is not set by default.

I also have successfully compiled upstream kernels with this option set in the past, and it worked fabulously. I'd just like to have the ondemand governor by default in *Ubuntu* kernels -- it just makes no sense to boot or e.g. check filesystems on full CPU frequency, because both is heavily I/O related. IMHO.

tags: removed: needs-upstream-testing
Revision history for this message
Björn Schließmann (b-schliessmann) wrote :

Sorry if this is against policies, please advise how else to do this properly. Marking "confirmed" since upstream testing figuratively occurred and no more input should be needed; though automatic expiry is still active.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Björn Schließmann (b-schliessmann) wrote :

So ... almost one year has passed ... I'm still open to suggestions, opinions, rants or flames.

Revision history for this message
penalvch (penalvch) wrote :

Björn Schließmann, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command in the development release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.

Please let us know your results. Thanks in advance.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.