public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* RE: cpufreq stops working after a while
@ 2006-08-11 21:38 Pallipadi, Venkatesh
  2006-08-11 21:53 ` Mark Lord
  0 siblings, 1 reply; 24+ messages in thread
From: Pallipadi, Venkatesh @ 2006-08-11 21:38 UTC (permalink / raw)
  To: Mark Lord; +Cc: Dave Jones, Linux Kernel, Andrew Morton

 

>-----Original Message-----
>From: Mark Lord [mailto:lkml@rtr.ca] 
>Sent: Friday, August 11, 2006 2:25 PM
>To: Pallipadi, Venkatesh
>Cc: Dave Jones; Linux Kernel; Andrew Morton
>Subject: Re: cpufreq stops working after a while
>
>Mark Lord wrote:
>>
>>> Venki wrote:
>>> Looks like there are thermal events happening that is 
>causing CPU limits
>>> to reduce. Are you running anything on the CPU when this happens. Is
>>> there a thermal interface in /proc/acpi that can give you 
>the current
>>> temperature of the system?
>> 
>> There are thermal thingies in /proc, and I'm watching the temperature
>> value from there (62C --> 65C), and the trip_points value is 95C..
>> 
>> Think it's thermal?
>
>Yup, thermal.
>Trips shortly after I see 66C in 
>/proc/acpi/thermal_zone/THM/temperature
>
>If I stop number crunching for a bit, the temperature drops down to the
>low 50's, and the max freq then gets set back to 1100.
>
>Mmmm.. is there a way to control the high/low thermostat values there?
>
>Cheers

What is the "cooling mode" you have in
/proc/acpi/thermal_zone/THM/cooling_mode.
Output of all files in that directory will help.

Thanks,
Venki

^ permalink raw reply	[flat|nested] 24+ messages in thread
* RE: cpufreq stops working after a while
@ 2006-08-11 22:18 Pallipadi, Venkatesh
  0 siblings, 0 replies; 24+ messages in thread
From: Pallipadi, Venkatesh @ 2006-08-11 22:18 UTC (permalink / raw)
  To: Mark Lord; +Cc: Dave Jones, Linux Kernel, Andrew Morton

 

>-----Original Message-----
>From: Mark Lord [mailto:lkml@rtr.ca] 
>Sent: Friday, August 11, 2006 2:54 PM
>To: Pallipadi, Venkatesh
>Cc: Dave Jones; Linux Kernel; Andrew Morton
>Subject: Re: cpufreq stops working after a while
>
>Pallipadi, Venkatesh wrote:
>>> Mark Lord wrote:
>>> Yup, thermal.
>>> Trips shortly after I see 66C in 
>>> /proc/acpi/thermal_zone/THM/temperature
>>>
>>> If I stop number crunching for a bit, the temperature drops 
>down to the
>>> low 50's, and the max freq then gets set back to 1100.
>>>
>>> Mmmm.. is there a way to control the high/low thermostat 
>values there?
>..
>> What is the "cooling mode" you have in
>> /proc/acpi/thermal_zone/THM/cooling_mode.
>> Output of all files in that directory will help.
>
>/proc/acpi/thermal_zone/THM/cooling_mode:
>	<setting not supported>
>	cooling mode:   critical
>
>/proc/acpi/thermal_zone/THM/polling_frequency:
>	<polling disabled>
>
>/proc/acpi/thermal_zone/THM/state:
>	state:                   ok
>
>/proc/acpi/thermal_zone/THM/temperature:
>	temperature:             49 C
>
>/proc/acpi/thermal_zone/THM/trip_points:
>	critical (S5):           95 C
>
>==========
>
>This is a passively cooled notebook, so there's no fan
>to control.  They probably self-limit the CPU speed when
>the temperature gets high to prevent meltdown of the drive.
>
>But I would like to raise the lower limit if possible,
>allowing the speed to bump back up at, say 58C rather
>than waiting for 52C as it currently does.
>
>??

Passive cooling starting temperature is given by platform manufacturer
through BIOS. You can check whether your BIOS has any option to change
it. Changing it manually by custom DSDT etc may be risky :).
One thing you can try from software is the polling_frequency above. For
some reason it is set to zero above. Try setting it to 1 sec and see
whether that makes any difference (echo 1 >
/proc/acpi/thermal_zone/THM/polling_frequency).

Venki

^ permalink raw reply	[flat|nested] 24+ messages in thread
* RE: cpufreq stops working after a while
@ 2006-08-11 21:08 Pallipadi, Venkatesh
  0 siblings, 0 replies; 24+ messages in thread
From: Pallipadi, Venkatesh @ 2006-08-11 21:08 UTC (permalink / raw)
  To: Mark Lord, Dave Jones; +Cc: Linux Kernel, Andrew Morton

 

>-----Original Message-----
>From: Mark Lord [mailto:lkml@rtr.ca] 
>Sent: Friday, August 11, 2006 1:30 PM
>To: Dave Jones
>Cc: Pallipadi, Venkatesh; Linux Kernel; Andrew Morton
>Subject: Re: cpufreq stops working after a while
>
>Pallipadi, Venkatesh wrote:
>>> Dave Jones wrote:
>>>> boot with cpufreq.debug=7, and capture dmesg output after it fails
>>>> to transition.  This might be another manifestation of the 
>mysterious
>>>> "highest frequency isnt accessable" bug, that seems to come from
>>>> some recent change in acpi.
>..
>> You also need to configure in CONFIG_CPU_FREQ_DEBUG
>
>Thanks, Venki!
>
>Okay, here's the tail end of the trace, in which (search for "max")
>one can see the top frequency limit being downgraded.
>
>But, by whom, and why ??
>And what's with these requests for oddball frequencies ("685714"),
>or is that just normal approximation within the governor?
>
>
>[  853.228000] cpufreq-core: updating policy for CPU 0
>[  853.228000] cpufreq-core: Warning: CPU frequency out of 
>sync: cpufreq and timing core thinks of 1100000, is 800000 kHz.
>[  853.228000] cpufreq-core: notification 0 of frequency 
>transition to 800000 kHz
>[  853.228000] userspace: saving cpu_cur_freq of cpu 0 to be 800000 kHz
>[  853.228000] cpufreq-core: notification 1 of frequency 
>transition to 800000 kHz
>[  853.228000] cpufreq-core: scaling loops_per_jiffy to 
>3195840 for frequency 800000 kHz
>[  853.228000] userspace: saving cpu_cur_freq of cpu 0 to be 800000 kHz
>[  853.228000] cpufreq-core: setting new policy for CPU 0: 
>600000 - 1100000 kHz
>[  853.228000] freq-table: request for verification of policy 
>(600000 - 1100000 kHz) for cpu 0
>[  853.228000] freq-table: verification lead to (600000 - 
>1100000 kHz) for cpu 0
>[  853.228000] freq-table: request for verification of policy 
>(600000 - 800000 kHz) for cpu 0
>[  853.228000] freq-table: verification lead to (600000 - 
>800000 kHz) for cpu 0
>[  853.228000] cpufreq-core: new min and max freqs are 600000 
>- 800000 kHz
>[  853.228000] cpufreq-core: governor: change or update limits
>[  853.228000] cpufreq-core: __cpufreq_governor for CPU 0, event 3

Looks like there are thermal events happening that is causing CPU limits
to reduce. Are you running anything on the CPU when this happens. Is
there a thermal interface in /proc/acpi that can give you the current
temperature of the system?

Thanks,
Venki

^ permalink raw reply	[flat|nested] 24+ messages in thread
* RE: cpufreq stops working after a while
@ 2006-08-11 19:55 Pallipadi, Venkatesh
  2006-08-11 20:29 ` Mark Lord
  0 siblings, 1 reply; 24+ messages in thread
From: Pallipadi, Venkatesh @ 2006-08-11 19:55 UTC (permalink / raw)
  To: Mark Lord, Dave Jones, Linux Kernel, Andrew Morton



>-----Original Message-----
>From: linux-kernel-owner@vger.kernel.org 
>[mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of Mark Lord
>Sent: Friday, August 11, 2006 12:41 PM
>To: Dave Jones; Linux Kernel; Andrew Morton
>Subject: Re: cpufreq stops working after a while
>
>Dave Jones wrote:
>> 
>> boot with cpufreq.debug=7, and capture dmesg output after it fails
>> to transition.  This might be another manifestation of the mysterious
>> "highest frequency isnt accessable" bug, that seems to come from
>> some recent change in acpi.
>
>booting with that option doesn't seem to give me any new messages
>in dmesg (or /var/log/messages).  I also tried editing cpufreq.c
>and hardcoding debug = 7 on the variable declaration.
>Still no new messages.
>
>??

You also need to configure in CONFIG_CPU_FREQ_DEBUG for the parameter to
take effect.

Thanks,
Venki

^ permalink raw reply	[flat|nested] 24+ messages in thread
* cpufreq stops working after a while
@ 2006-08-11 18:25 Mark Lord
  2006-08-11 18:39 ` Dave Jones
  2006-08-11 18:46 ` Andrew Morton
  0 siblings, 2 replies; 24+ messages in thread
From: Mark Lord @ 2006-08-11 18:25 UTC (permalink / raw)
  To: Linux Kernel; +Cc: Andrew Morton

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?  And how can I fix it?


^ permalink raw reply	[flat|nested] 24+ messages in thread
end of thread, other threads:[~2006-08-24 16:15 UTC | newest]

Thread overview: 24+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-08-11 21:38 cpufreq stops working after a while Pallipadi, Venkatesh
2006-08-11 21:53 ` Mark Lord
  -- strict thread matches above, loose matches on Subject: below --
2006-08-11 22:18 Pallipadi, Venkatesh
2006-08-11 21:08 Pallipadi, Venkatesh
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 18:25 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:10   ` Mark Lord
2006-08-11 19:18     ` Andrew Morton

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox