frequency scaling on P4 does not work

Bug #460064 reported by dmatt
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
cpufreqd
New
Undecided
Unassigned
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Fresh install of Kubuntu Karmic RC on old notebook with Intel P4 CPU, frequency scaling does not work on live CD nor on permanent install. There is no sign any scaling is available at all. Scaling works in Hardy on other partition.

ProblemType: Bug
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: A5451 [ALI 5451], device 0: ALI 5451 [ALI 5451]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ubik 1448 F.... knotify4
                      ubik 1479 F.... kmix
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'A5451'/'ALI 5451 at 0x1000, irq 5'
   Mixer name : 'Conexant Cx20468 rev 1,Conexant Cx20468 rev 1'
   Components : 'AC97a:43585429 AC97m:43585429'
   Controls : 25
   Simple ctrls : 18
Date: Sat Oct 24 23:51:51 2009
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=d8ff7fdb-fed5-49b9-960b-c01de7a9007f
InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release Candidate i386 (20091020.2)
Lsusb:
 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
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Hewlett-Packard Pavilion ze8500 (DJ317T)
Package: linux-image-2.6.31-14-generic 2.6.31-14.48
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   3.3V 32-bit PC Card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-14-generic root=UUID=71df378d-ff42-4dc5-90fa-44048ba02725 ro quiet splash
ProcEnviron:
 LANGUAGE=
 LANG=sk_SK.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-14-generic N/A
 linux-firmware 1.24
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
Uname: Linux 2.6.31-14-generic i686
dmi.bios.date: 05/03/2005
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: KF_KH.F.25
dmi.board.name: 0850
dmi.board.vendor: Hewlett-Packard
dmi.board.version: NS570 Version PQ1B60
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrKF_KH.F.25:bd05/03/2005:svnHewlett-Packard:pnPavilionze8500(DJ317T):pvrKH.F.25:rvnHewlett-Packard:rn0850:rvrNS570VersionPQ1B60:cvnHewlett-Packard:ct10:cvrN/A:
dmi.product.name: Pavilion ze8500 (DJ317T)
dmi.product.version: KH.F.25
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
dmatt (martind) wrote :
Revision history for this message
crackbaby (edwardsp) wrote :

Same problem here, I think. Worked in Intrepid.

$ cpufreq-info
CPU 0:
(...)
current policy: frequency should be within 400 MHz and 3.20 GHz.
The governor "performance" may decide which speed to use
within this range.
(...)
CPU 1:
current policy: frequency should be within 400 MHz and 3.20 GHz.
The governor "performance" may decide which speed to use
within this range.
(...)

$ sudo cpufreq-set -c0 -g ondemand
$ sudo cpufreq-set -c1 -g ondemand

cpufreq-info still lists performance as the gov in charge...
No errors, no warnings, just no apparent change of governor.

$ cpufreq-info |grep "available cpu"
  available cpufreq governors: conservative, ondemand, userspace, powersave, performance

$ lsmod |grep p4_
p4_clockmod 4164 1

dmatt (martind)
Changed in linux (Ubuntu):
status: New → Invalid
Revision history for this message
dmatt (martind) wrote :

I marked this bug as invalid. I was able to verify with "powertop", that frequency scaling is indeed working on final version of Karmic in my case.
I suggest to report bug described in #2 in a separate bug report. "p4_clockmod" module is not used at all in my case.

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.