On Fri, Sep 29, 2006 at 02:35:43PM -0700, Pallipadi, Venkatesh wrote: > cpufreq_cpu_data[] = NULL; only happens when acpi_cpufreq driver init > fails; > Looks like acpi_cpufreq driver init is failing at some point in this > case and the driver is staying loaded after that failure. That in turn > seems similar to one other bug I saw recently. Ah, that was because it was marked CPUFREQ_STICKY in 2.6.18. That was added to work around another problem : If it was built modular, a modprobe acpi-cpufreq would be really noisy when it get an -ENODEV Dave
