[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070825001454.GA23622@redhat.com>
Date: Fri, 24 Aug 2007 20:14:54 -0400
From: Dave Jones <davej@...hat.com>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Tilman Schmidt <tilman@...p.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,
Thomas Renninger <trenn@...e.de>,
Venkatesh Pallipadi <venkatesh.pallipadi@...el.com>
Subject: Re: 2.6.23-rc3-mm1
On Fri, Aug 24, 2007 at 05:07:02PM -0700, Andrew Morton wrote:
> > FATAL: Error inserting processor (/lib/modules/2.6.23-rc3-mm1-testing/kernel/drivers/acpi/processor.ko): Input/output error
> > WARNING: Error inserting processor (/lib/modules/2.6.23-rc3-mm1-testing/kernel/drivers/acpi/processor.ko): Input/output error
> >
> > 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?
More likely, he was using a cpufreq driver that required acpi
functionality, and because processor.ko went boom, the house of cards
came tumbling down.
I long for the olde days when acpi changes didn't end up with
finger pointing at cpufreq.
Dave
--
http://www.codemonkey.org.uk
-
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