>-----Original Message----- >From: cpufreq-bounces@xxxxxxxxxxxxxxxxxx >[mailto:cpufreq-bounces@xxxxxxxxxxxxxxxxxx] On Behalf Of Dave Jones >Sent: Friday, August 18, 2006 11:44 AM >To: Alexey Starikovskiy >Cc: Brown, Len; linux-acpi@xxxxxxxxxxxxxxx; cpufreq@xxxxxxxxxxxxxxxxxx >Subject: acpi-cpufreq oddness > >Someone reported to me that modprobe acpi-cpufreq now fails noisily >complaining about invalid arguments. I was able to reproduce it >on one of my boxes that doesn't have any form of speed scaling at all. >Previously, the modprobe would return with -ENODEV, but now its >getting an -EINVAL from somewhere. (I'm still trying to chase down >exactly where its coming from). > >So far in chasing this, all I found is a cosmetic bug, >acpi_cpufreq_target has a.. >dprintk("acpi_cpufreq_setpolicy"); >in it, which is the only reference to setpolicy in the whole driver. > >I don't have handy access to a git tree at the moment, and >I've forgotten >the history of the recent changes here. > >Alexey/Len, any ideas whats going on here? > > Dave > Does the error say "Invalid _PSD data" or something similar. Seems to be a side-effect of earlier software co-ordination patchset. If this is the error you are seeing, I will send in a quick patch to fix it. Thanks, Venki - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
