[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <653FFBB4508B9042B5D43DC9E18836F5014D954E@scsmsx415.amr.corp.intel.com>
Date: Fri, 24 Aug 2007 17:13:37 -0700
From: "Pallipadi, Venkatesh" <venkatesh.pallipadi@...el.com>
To: "Andrew Morton" <akpm@...ux-foundation.org>,
"Tilman Schmidt" <tilman@...p.cc>
Cc: <linux-kernel@...r.kernel.org>,
"Thomas Gleixner" <tglx@...utronix.de>,
"john stultz" <johnstul@...ibm.com>, "Andi Kleen" <ak@...e.de>,
"Len Brown" <lenb@...nel.org>, <linux-acpi@...r.kernel.org>,
"Dave Jones" <davej@...emonkey.org.uk>,
"Thomas Renninger" <trenn@...e.de>
Subject: RE: 2.6.23-rc3-mm1
>> - in /var/log/warn:
>>
>> Aug 25 00:44:00 xenon powersaved[5356]: WARNING
>(CpufreqManagement:51) No capability cpufreq_control
>> Aug 25 00:44:00 xenon powersaved[5356]: WARNING
>(CpufreqManagement:51) No capability cpufreq_control
>
>Dunno, there're some significant-looking cpufreq changes in
>there, such as
>cpufreq-allow-ondemand-and-conservative-cpufreq-governors-to-be
>-used-as-default.patch.
>Maybe we went and chose a different governor for you?
>
This is probably not related to cpufreq changes itself. Looks like it is
coming due to
>> FATAL: Error inserting processor
>(/lib/modules/2.6.23-rc3-mm1-testing/kernel/drivers/acpi/proces
>sor.ko): Input/output error
>> WARNING: Error inserting processor
>(/lib/modules/2.6.23-rc3-mm1-testing/kernel/drivers/acpi/proces
>sor.ko): Input/output error
Not sure why this is failing though. Don't recall any significant
changes in processor.ko recently apart from CPUIDLE stuff.
Thanks,
Venki
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists