RE: 2.6.19-rc5-mm2

[Pallipadi, Venkatesh]

>-----Original Message-----
>From: Gautham R Shenoy [mailto:ego@xxxxxxxxxx] 
>Sent: Wednesday, November 15, 2006 2:34 AM
>To: Gautham R Shenoy; Reuben Farrelly; Andrew Morton; 
>davej@xxxxxxxxxx; linux-kernel@xxxxxxxxxxxxxxx; Pallipadi, 
>Venkatesh; CPUFreq Mailing List
>Subject: Re: 2.6.19-rc5-mm2
>
>Hi,
>
>On Tue, Nov 14, 2006 at 09:58:29PM +0100, Mattia Dongili wrote:
>> 
>> maybe this helps? mostly guessing here, but when cpufreq_userspace is
>> the default governor we may hit this path and leave policy->cur
>> unset.
>
>I doubt if that's causing the problem. My reasons are:
>
>- Reuben's config shows his system to be a x64_64. So if I am not
>  mistaken, the correct file look for would be 
>  arch/ia64/kernel/cpufreq/acpi-cpufreq.c.

ia64 and x86_64 are different!
X86_64 shares acpi-cpufreq.c in arch/i386/kernel/cpu/cpufreq. So, that
is the file that can be causing problems here.

>- The fix provided by you deals with the state of a 
>  driver(hardware) specific variable data->cpu_feature while the
>  governors like userspace/performance/powersave/ondemand are 
>  driver(hardware) independent.
>
>Nevertheless, it could be a valid fix for i386 acpi_cpufreq considering
>that policy->cur is not being initialized if 
>data->cpu_feature == ACPI_ADR_SPACE_FIXED_HARDWARE.

Yes. Patch from Mattia is indeed required for acpi-cpufreq. 
Mattia: Can you please send the patch towards Andrew (With signed off
etc) for inclusion.

Reuben: Can you please enable CPU_FREQ_DEBUG in your config and boot
with "cpufreq.debug=7" boot parameter and send me the log. That will
give some more debug information that should help to root cause this
faster.

Thanks,
Venki
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/