http://bugzilla.kernel.org/show_bug.cgi?id=10952





------- Comment #2 from [EMAIL PROTECTED]  2008-06-22 19:34 -------
hmm, I think you can add a dump_stack in cpu_update_policy to see who is
keeping on changing the scaling_max_freq?
something like:
---
 drivers/cpufreq/cpufreq.c |    1 +
 1 file changed, 1 insertion(+)

Index: linux-2.6/drivers/cpufreq/cpufreq.c
===================================================================
--- linux-2.6.orig/drivers/cpufreq/cpufreq.c    2008-06-17 06:35:42.000000000
+0800
+++ linux-2.6/drivers/cpufreq/cpufreq.c 2008-06-23 10:25:13.000000000 +0800
@@ -1722,6 +1722,7 @@
        if (unlikely(lock_policy_rwsem_write(cpu)))
                return -EINVAL;

+       dump_stack();
        dprintk("updating policy for CPU %u\n", cpu);
        memcpy(&policy, data, sizeof(struct cpufreq_policy));
        policy.min = data->user_policy.min;


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla

Reply via email to