Dell XPS M1330 CPU scales down to 800 MHz

Hello Mark,

When the issue is present, could you please preform the following to provide more information to kernel developers. You will need to install the "powertop" package before doing this.

1) Open a terminal
2) Run the following command
$ while true; do false; done
3) Press Ctrl-Shift-T to open a new terminal tab
4) Run this command:
$ sudo powertop -d -t30 > ~/powertop_output.txt

Once powertop stops, please attach the powertop_output.txt file from your home directory into this bug.

Will do! Thanks for your assistance with this.

I've just installed powertop and will run the commands you mention the next
time I have this issue. I'd really like to get this sorted out as I'm a
huge fan of Ubuntu and it seems like this is an ongoing problem for me.

-mark

On Fri, Jul 16, 2010 at 10:37 AM, David Bensimon
<email address hidden>wrote:

> Hello Mark,
>
> When the issue is present, could you please preform the following to
> provide more information to kernel developers. You will need to install
> the "powertop" package before doing this.
>
> 1) Open a terminal
> 2) Run the following command
> $ while true; do false; done
> 3) Press Ctrl-Shift-T to open a new terminal tab
> 4) Run this command:
> $ sudo powertop -d -t30 > ~/powertop_output.txt
>
> Once powertop stops, please attach the powertop_output.txt file from
> your home directory into this bug.
>
> --
> Dell XPS M1330 CPU scales down to 800 MHz
> https://bugs.launchpad.net/bugs/605465
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “linux” package in Ubuntu: New
>
> Bug description:
> My Dell XPS M1330 regularly scales the CPU on demand for a few hours, then
> begins to scale the 2.4 GHz CPU down to 800 MHz as the day goes on.
> Selecting the performance profile will not cause the CPU to return to 2.4
> GHz.
>
> Selecting the older version 173 of the NVIDIA driver seemed to reduce the
> frequency of this issue, though it still occurred so I have returned to the
> latest driver release. I'm not sure it this is because the GPU was
> generating heat that was adversely affecting the performance of the CPU but
> I am monitoring the temperate of both CPU and GPU now and will watch to see
> what they are when this problem arises. Does Ubuntu ever force CPU scaling
> as the computer gets warmer?
>
> I've included an attachment describing my CPU information to this bug.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 10.04
> Package: linux-image-2.6.32-23-generic 2.6.32-23.37
> Regression: No
> Reproducible: No
> ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5
> Uname: Linux 2.6.32-23-generic x86_64
> NonfreeKernelModules: nvidia
> AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: mark 1799 F.... pulseaudio
> /dev/snd/pcmC0D0p: mark 1799 F...m pulseaudio
> CRDA: Error: [Errno 2] No such file or directory
> Card0.Amixer.info:
> Card hw:0 'Intel'/'HDA Intel at 0xf6ffc000 irq 21'
> Mixer name : 'SigmaTel STAC9228'
> Components : 'HDA:83847616,10280209,00100201'
> Controls : 28
> Simple ctrls : 18
> Date: Wed Jul 14 09:08:12 2010
> Frequency: Once a day.
> HibernationDevice: RESUME=UUID=a0a67dc1-f975-484f-8666-4097a1b81276
> InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
> MachineType: Dell Inc. XPS M1330
> ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-23-generic
> root=UUID=84ef7af6-2c90-4015-834c-f0fefb44c0a9 ro quiet splash
> ProcEnviron:
> PATH=(custom, user)
> LANG=en_CA.utf8
> SHELL=/bin/bash
> RelatedPackageVersion...

Hi Mark,

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.]

Hi Jeremy:

I'm heading out to the lake for a few weeks and will have limited access to the internet. I'm leaving in a few hours but will try to test this as soon as I'm back in the start of August!

Thank-you for all your help. You guys do great work!

Just took a quick look at the wiki. Is it possible to do this kernel testing with a live image? I'm experiencing this issue on a laptop used for production development so re-formatted the machine, or permanently installing a mainline kernel isn't the best option.

Can you please confirm which kernel to install. Is the Linus kernel the one you'd like me to test with?

As requested I've run powertop while experiencing this issue. I ran it three times. Once immediately as the issue was happening, then again with after using the CPU scaling widget to select performance mode, and ondemand mode. See attachments (powertop_output.txt, powertop_output_performance.txt, and powertop_output_ondemand.txt)

As requested I've run powertop while experiencing this issue. I ran it three times. Once immediately as the issue was happening, then again with after using the CPU scaling widget to select performance mode, and ondemand mode. See attachments (powertop_output.txt, powertop_output_performance.txt, and powertop_output_ondemand.txt)

The output of:

sudo powertop -d -t30 > ~/powertop_output_performance.txt

Output of:

sudo powertop -d -t30 > ~/powertop_output_performance.txt

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu development release http://cdimage.ubuntu.com/daily-live/current/ . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

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