CPU stuck at lowest speed after 16min from boot

Bug #396432 reported by Tim
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Medium
Unassigned
Nominated for Lucid by Charlie Kravetz

Bug Description

I have a Fujitsu Lifebook S6510 with a intel t7250 @2GHz running LinuxMint 7 (Ubuntu Jaunty 9.04 based)

My problem is that after 16min since boot the scaling_max_freq get set to 800MHz and nothing I do can change this.
I have tried becoming root and echoing, writing scripts, using different governors, etc, nothing changes it.

I have also tried adjusting BIOS settings, AC power and no AC power, all to no affect.

The only way that I have found that "occasionally" gets back full speed without rebooting is to suspend to ram and then when it comes out of suspend it "may" be running at normal speed.

The only remotely interesting thing that I have come up with was while cross referencing with the log files I found this line in /var/log/kern.log:
Jul 6 08:50:12 light kernel: [ 921.099374] Monitor-Mwait will be used to enter C-3 state

After writing a script to monitor scaling_max_freq and kern.log I found that it was always when this line appears in the log that the frequency gets locked.

I am guessing that this is a bug in the kernel (namely, cpufreq module) but I don't know for certain.

This bug has been present and all ubuntu installation (and live cd's) that I have tried recently, this includes ubuntu karmic alpha 2 Xubuntu Jaunty and LinuxMint 6 (Ubuntu intrepid 8.10 based).

I hope some one has some idea about this, ti has really got me stuck.
Tim

the only other thing in the log t hat might be of any interest is this:
Jul 6 08:35:09 light kernel: [ 1.239494] Monitor-Mwait will be used to enter C-1 state
Jul 6 08:35:09 light kernel: [ 1.239497] Monitor-Mwait will be used to enter C-2 state
Jul 6 08:35:09 light kernel: [ 1.239500] Monitor-Mwait will be used to enter C-3 state

Note that althought the last line there is the same as the line when the cpu gets locked, the cpu does not get locked during boot.

This bug is not a once off bug, it happens every time I boot my computer.
The time the that line appears in the log the is when the cpu gets locked is always at a very similar time, but always slightly different (925s, 921s, 929s, etc).

Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We need some more information from you before we can start working on this bug.

Please run the following command which will attach necessary information:

apport-collect -p linux-image-`uname -r` 396432
if you are using Jaunty Jackalope (9.04)

Bear in mind that you may need to install the python-launchpadlib package from the universe repository with 'sudo apt-get install python-launchpadlib'. Additionally, when prompted to give apport-collect permissions for Launchpad you will need to give it at least the ability to "Change Non-Private" data as it will be adding information to your bug report.

If you are using an older release or cannot use apport please at least add the following information (pay attention to lspci's additional options):
First run the following commands:
1) uname -a > uname-a.log
2) dmesg > dmesg.log
3) sudo lspci -vvnn > lspci-vvnn.log
4) cat /proc/version_signature > version.log
then attach the files separately to the bug report (not pasted into comments or tar/zip-ed).

For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies. Thanks in advance!

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Tim (tim-a-webb) wrote : apport-collect data

Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC262 Analog [ALC262 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: timothy 2416 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfc700000 irq 21'
   Mixer name : 'Realtek ALC262'
   Components : 'HDA:10ec0262,10cf0100,00100202 HDA:11c11040,11c10001,00100200'
   Controls : 27
   Simple ctrls : 16
DistroRelease: LinuxMint 8
HibernationDevice: RESUME=UUID=a4abe6dc-a61d-4166-9c9e-1f70938b5132
InstallationMedia: Linux Mint 8 "Helena" - Release i386 (20091027)
MachineType: FUJITSU S6511
Package: linux-image-2.6.31-19-generic 2.6.31-19.56
PackageArchitecture: i386
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.31-19-generic root=UUID=c9381be2-33ff-4b73-b726-cfe9ae8fe01c ro quiet splash
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_AU.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-19.56-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-19-generic N/A
 linux-firmware 1.25
Uname: Linux 2.6.31-19-generic i686
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare vboxusers
WifiSyslog:
 Feb 17 08:01:34 light kernel: [59279.104095] usb 5-1: new full speed USB device using uhci_hcd and address 4
 Feb 17 08:01:34 light kernel: [59279.289383] usb 5-1: configuration #1 chosen from 1 choice
 Feb 17 08:01:34 light kernel: [59279.296734] cdc_acm 5-1:1.0: This device cannot do calls on its own. It is not a modem.
 Feb 17 08:01:34 light kernel: [59279.296783] cdc_acm 5-1:1.0: ttyACM0: USB ACM device
XsessionErrors:
 (gnome-settings-daemon:2431): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:2431): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (polkit-gnome-authentication-agent-1:2547): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (nautilus:2538): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (gnome-panel:2535): Gdk-CRITICAL **: gdk_x11_colormap_foreign_new: assertion `GDK_IS_VISUAL (visual)' failed
dmi.bios.date: 09/27/2007
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: Version 1.17
dmi.board.name: FJNB1D3
dmi.board.vendor: FUJITSU
dmi.chassis.type: 10
dmi.chassis.vendor: D7E300E5084D1132
dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.17:bd09/27/2007:svnFUJITSU:pnS6511:pvr:rvnFUJITSU:rnFJNB1D3:rvr:cvnD7E300E5084D1132:ct10:cvr:
dmi.product.name: S6511
dmi.sys.vendor: FUJITSU

Revision history for this message
Tim (tim-a-webb) wrote : AlsaDevices.txt
Revision history for this message
Tim (tim-a-webb) wrote : AplayDevices.txt
Revision history for this message
Tim (tim-a-webb) wrote : BootDmesg.txt
Revision history for this message
Tim (tim-a-webb) wrote : Card0.Amixer.values.txt
Revision history for this message
Tim (tim-a-webb) wrote : Card0.Codecs.codec.0.txt
Revision history for this message
Tim (tim-a-webb) wrote : Card0.Codecs.codec.1.txt
Revision history for this message
Tim (tim-a-webb) wrote : CurrentDmesg.txt
Revision history for this message
Tim (tim-a-webb) wrote : Dependencies.txt
Revision history for this message
Tim (tim-a-webb) wrote : IwConfig.txt
Revision history for this message
Tim (tim-a-webb) wrote : Lspci.txt
Revision history for this message
Tim (tim-a-webb) wrote : Lsusb.txt
Revision history for this message
Tim (tim-a-webb) wrote : PciMultimedia.txt
Revision history for this message
Tim (tim-a-webb) wrote : ProcCpuinfo.txt
Revision history for this message
Tim (tim-a-webb) wrote : ProcInterrupts.txt
Revision history for this message
Tim (tim-a-webb) wrote : ProcModules.txt
Revision history for this message
Tim (tim-a-webb) wrote : RfKill.txt
Revision history for this message
Tim (tim-a-webb) wrote : UdevDb.txt
Revision history for this message
Tim (tim-a-webb) wrote : UdevLog.txt
Changed in linux (Ubuntu):
status: Incomplete → New
tags: added: apport-collected
Revision history for this message
Tim (tim-a-webb) wrote :

Note that due to the the fact the I reported this bug some time ago, some of the properties of the bug may have changed.
I am now using Linux Mint 8 (Ubuntu 9.10 based) and the bug is still present. I have not tested this version for all the same log file lines, but I will do so as soon as I can.

I have not tested Ubuntu 10.04 for the bug, I will do so as soon as I can.

Note that suspending to ram and the waking reliably restores the CPU to normal operation.

Tim

Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

Thanks for for testing this issue in the latest release. And thanks for the attachments. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here. Thanks again for taking the time to make Ubuntu better!

Changed in linux (Ubuntu):
status: New → Confirmed
importance: Undecided → Medium
Revision history for this message
Tim (tim-a-webb) wrote :

I have tested this more carefully on LIinux Mint 8 (Ubuntu 9.10 based) and confirmed that the lock to lowest clock rate coincides with a line similar to this in /var/logs/kern.log:
Feb 17 21:20:27 light kernel: [ 1583.863654] Monitor-Mwait will be used to enter C-3 state
Note that this was about 24 minutes after boot not 16 minutes. I know what that might mean.

I have also confirmed that this bug is in Ubuntu Lucid (Ubuntu 10.4) alpha 2. In this case it did occur about 16 minutes after boot.

Tim

Revision history for this message
Tim (tim-a-webb) wrote :

Should I run apport on Ubuntu Lucid as well?

Tim

Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

Let's see what the developers request, okay. The logs attached already may be adequate, and if they are, more just get in the way. Thanks.

tags: added: lucid
Revision history for this message
Tim (tim-a-webb) wrote :

Note that a sentence I wrote in post 23 should have read "I don't know what that might mean" and not "I know what that might mean".

Revision history for this message
Johannes H. Jensen (joh) wrote :

I experience the same issue on my ThinkPad X61 running 10.04. Let me know if you'd like me to run apport-collect as well. The problem typically occurs during video playback - after a while the cpu frequency is stuck at 800Mhz resulting in choppy playback at best.

Revision history for this message
Mark (mge7272-ubuntu) wrote :

This issue is affecting my Dell Vostro 1400 Laptop. Interestingly, it didn't affect the laptop when I had an Nvidia 8400GS video card in the laptop. In the last week I replaced the motherboard and video card with an integrated Intel GM965 X3100 card and now have the problem with the cpu stuck at the slowest speed.

Revision history for this message
Lord_JABA (lordjaba) wrote :

I got similar problem on dell precison m70. And i have a question about that:
i got frequency monitor applet- does it is any thing i can do to make manual settings work?
Is there a way to set cpu to always run on full speed on AC power.

Revision history for this message
Lord_JABA (lordjaba) wrote :

Also cpu never goes to full speed (2.13GHz) im stuck with max 1.87. Have 2.13 on frequency list.
cpufreq-selector -f 2130000 don't do anything

Revision history for this message
Lord_JABA (lordjaba) wrote :

sorry but one more question- i have ubuntu 10.04- what deamon controls my cpu freq i don't have powernowd cpufreqd? Where is any .config file i can mess with ? i want to change thresholds etc

Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

Thanks for helping improve Ubuntu. Unless you have exactly the same hardware as the original report, you should file a new bug report for your issue. You can do that easily by opening a terminal and typing "ubuntu-bug linux". That will automatically open a new bug report in launchpad and attach all of the pertinent log files for the developers to examine.

Revision history for this message
Brad Figg (brad-figg) wrote : Unsupported series, setting status to "Won't Fix".

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: Confirmed → Won't Fix
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.