From: Mark Lord <lkml@rtr.ca>
To: Andrew Morton <akpm@osdl.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>, cpufreq@www.linux.org.uk
Subject: Re: cpufreq stops working after a while
Date: Fri, 11 Aug 2006 15:10:16 -0400 [thread overview]
Message-ID: <44DCD618.2040700@rtr.ca> (raw)
In-Reply-To: <20060811114631.4a699667.akpm@osdl.org>
Andrew Morton wrote:
> On Fri, 11 Aug 2006 14:25:26 -0400
> Mark Lord <lkml@rtr.ca> wrote:
>
>> One of my notebooks (Dell Latitude X1) has a 1.1GHz Pentium-M ULV processor.
>> This chip can change CPU speeds from 600 -> 800 -> 1100 Mhz.
>>
>> I use speedstep-centrino with it, and after boot all is usually okay.
>> But after a few hours of operation, it stops shifting to the highest frequency
>> even under continuous 100% load (or not). Eventually it gets stuck at 600Mhz
>> and stays there until I reboot.
>>
>> Sometimes rebooting doesn't even restore it.
>>
>> /sys/devices/system/cpu/cpu0/cpufreq is all very normal looking,
>> showing the available frequencies and other info. All of the attribs
>> there look fine, except for "scaling_max_freq", which is what seems
>> to gradually get set smaller. For instance, right now it is set to 800000,
>> and it won't let me change it (echo 11000000 > scaling_max_freq has no effect.
>>
>> WHY?
>
> cpufreq seems to have relatively frequent problems.
>
>> And how can I fix it?
>
> You could start by telling us which kernel versions are affected ;)
Mmm.. since it appears to be related, kbuild dumps this out when building the kernel:
WARNING: drivers/acpi/processor.o - Section mismatch: reference to .init.data: from .text between 'acpi_processor_power_init' (at offset 0xf29) and 'acpi_processor_cst_has_changed'
A possible source for the bug, or total red herring ?
next prev parent reply other threads:[~2006-08-11 19:10 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-11 18:25 cpufreq stops working after a while Mark Lord
2006-08-11 18:39 ` Dave Jones
2006-08-11 19:41 ` Mark Lord
2006-08-11 20:01 ` Mark Lord
2006-08-11 20:12 ` Dave Jones
2006-08-11 18:46 ` Andrew Morton
2006-08-11 19:01 ` Mark Lord
2006-08-11 19:01 ` Mark Lord
2006-08-11 19:10 ` Mark Lord [this message]
2006-08-11 19:18 ` Andrew Morton
2006-08-12 8:52 ` Erik Slagter
2006-08-15 7:49 ` Thomas Renninger
2006-08-15 11:07 ` Carlos Garcia Campos
-- strict thread matches above, loose matches on Subject: below --
2006-08-11 19:55 Pallipadi, Venkatesh
2006-08-11 20:29 ` Mark Lord
2006-08-11 20:39 ` Mark Lord
2006-08-11 21:01 ` Dave Jones
2006-08-11 21:09 ` Mark Lord
2006-08-11 21:15 ` Mark Lord
2006-08-11 21:17 ` Mark Lord
2006-08-11 21:25 ` Mark Lord
2006-08-18 15:11 ` Pavel Machek
2006-08-24 14:44 ` Mark Lord
2006-08-24 16:15 ` Matthew Garrett
2006-08-11 21:08 Pallipadi, Venkatesh
2006-08-11 21:38 Pallipadi, Venkatesh
2006-08-11 21:53 ` Mark Lord
2006-08-11 22:18 Pallipadi, Venkatesh
2006-08-15 13:27 Pallipadi, Venkatesh
2006-08-15 15:07 ` Carlos Garcia Campos
2006-08-16 19:28 ` Len Brown
2006-08-15 15:23 Pallipadi, Venkatesh
2006-08-15 17:46 ` Carlos Garcia Campos
2006-08-16 10:10 ` Carlos Garcia Campos
2006-08-16 13:27 Pallipadi, Venkatesh
2006-08-16 18:19 ` Carlos Garcia Campos
2006-08-17 10:46 ` Thomas Renninger
2006-08-17 10:58 ` Carlos Garcia Campos
2006-08-17 15:28 ` Thomas Renninger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44DCD618.2040700@rtr.ca \
--to=lkml@rtr.ca \
--cc=akpm@osdl.org \
--cc=cpufreq@www.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.