eeePC 700 Celeron: ondemand and conservative governor didn't work

Bug #588019 reported by Sebastian Bator
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Since Karmic the scaling governor for the Celeron prozessor of my eeePC 700 (p4-clockmod) can not use the ondemand or conservative scaling governor. When I try to switch the kern.log puts out:

ondemand governor failed, too long transition latency of HW, fallback to performance governor

It is using the performance governor when pluged in and the powersave (meaning ~100 MHz) when on battery power, if p4-clockmod is loaded.

There are some bugs around with commends regarding this issue (#432706 and #433331) , but since the original reporters reported other issues I open this bug.

Especially interesting could be these comments even if some contradict each other:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/432706/comments/9
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/432706/comments/14
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/433331/comments/7
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/433331/comments/11

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-22-generic 2.6.32-22.33
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC662 rev1 Analog [ALC662 rev1 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC662 rev1 Analog [ALC662 rev1 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: user 1272 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf7eb8000 irq 16'
   Mixer name : 'Realtek ALC662 rev1'
   Components : 'HDA:10ec0662,104382a1,00100101'
   Controls : 13
   Simple ctrls : 8
Date: Mon May 31 21:19:26 2010
EcryptfsInUse: Yes
InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Beta i386 (20100406.1)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.

 ppp0 no wireless extensions.
MachineType: ASUSTeK Computer INC. 701
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=caa48be3-4fb5-4873-a114-07710157c454 ro splash
ProcEnviron:
 PATH=(custom, User Name)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.34
RfKill:
 0: eeepc-wlan: Wireless LAN
  Soft blocked: yes
  Hard blocked: no
SourcePackage: linux
WifiSyslog:
 May 31 21:07:21 silagu kernel: [ 6001.728232] p4-clockmod: P4/Xeon(TM) CPU On-Demand Clock Modulation available
 May 31 21:08:25 silagu kernel: [ 6066.209450] ondemand governor failed, too long transition latency of HW, fallback to performance governor
 May 31 21:09:55 silagu kernel: [ 6156.095417] p4-clockmod: P4/Xeon(TM) CPU On-Demand Clock Modulation available
dmi.bios.date: 03/03/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0910
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 701
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x00000000
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTek Computer INC.
dmi.chassis.version: x.x
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0910:bd03/03/2008:svnASUSTeKComputerINC.:pn701:pvrx.x:rvnASUSTeKComputerINC.:rn701:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x:
dmi.product.name: 701
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.

Revision history for this message
Sebastian Bator (eremit7) wrote :
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi eremit7,

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
Sebastian Bator (eremit7) wrote :

The problem still exists with the upstream kernel (2.6.35-999-generic). The error messages are pretty the same:

Jun 24 21:57:32 silagu kernel: [ 232.484072] ondemand governor failed, too long transition latency of HW, fallback to performance governor

Changed in linux (Ubuntu):
status: Incomplete → New
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Sebastian Bator, 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
Sebastian Bator (eremit7) wrote :

I am not able to start or install quantal alpha 3 on the eeePC.

I will try the stable release in the next days.

Revision history for this message
Sebastian Bator (eremit7) wrote :

Ubuntu does not boot on the eeePC, therefore I am unable to verify, if the problem persists. Since I am no longer using the affected computer, I have no problem with the janitor to take care of this report in 60 days and will not invest time in debugging the boot problems.

Revision history for this message
penalvch (penalvch) wrote :

Sebastian bator, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/588019/comments/6 regarding you no longer using the affected computer. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Incomplete → Invalid
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.