CPU stuck at lowest speed after 16min from boot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Won't Fix
|
Medium
|
Unassigned | ||
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).
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): signature > version.log
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_
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/ KernelTeamBugPo licies. Thanks in advance!