From: Dave Jones <davej@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Tilman Schmidt <tilman@imap.cc>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
john stultz <johnstul@us.ibm.com>, Andi Kleen <ak@suse.de>,
Len Brown <lenb@kernel.org>,
linux-acpi@vger.kernel.org, Thomas Renninger <trenn@suse.de>,
Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
Subject: Re: 2.6.23-rc3-mm1
Date: Fri, 24 Aug 2007 20:14:54 -0400 [thread overview]
Message-ID: <20070825001454.GA23622@redhat.com> (raw)
In-Reply-To: <20070824170702.a2c51084.akpm@linux-foundation.org>
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
next prev parent reply other threads:[~2007-08-25 0:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070822020648.5ea3a612.akpm@linux-foundation.org>
[not found] ` <46CF695D.1020008@imap.cc>
2007-08-25 0:07 ` 2.6.23-rc3-mm1 Andrew Morton
2007-08-25 0:13 ` 2.6.23-rc3-mm1 Pallipadi, Venkatesh
2007-08-25 0:38 ` 2.6.23-rc3-mm1 Pallipadi, Venkatesh
2007-08-25 23:26 ` 2.6.23-rc3-mm1 Tilman Schmidt
2007-08-25 23:57 ` 2.6.23-rc3-mm1 Randy Dunlap
2007-08-27 13:35 ` 2.6.23-rc3-mm1 Tilman Schmidt
2007-08-25 0:14 ` Dave Jones [this message]
2007-08-25 0:21 ` 2.6.23-rc3-mm1 john stultz
2007-08-25 22:39 ` 2.6.23-rc3-mm1 Tilman Schmidt
2007-08-25 0:47 ` 2.6.23-rc3-mm1 Tilman Schmidt
2007-08-25 3:30 ` 2.6.23-rc3-mm1 Andrew Morton
2007-08-25 4:28 ` 2.6.23-rc3-mm1 Dave Jones
2007-08-25 7:55 ` 2.6.23-rc3-mm1 Paul Rolland
2007-08-25 23:37 ` 2.6.23-rc3-mm1 Tilman Schmidt
2007-09-05 20:41 ` Clock trouble retest results with 2.6.23-rc4-mm1 (was: 2.6.23-rc3-mm1) Tilman Schmidt
2007-08-27 21:27 ` [-mm patch] make "struct menu_governor" static (again) Adrian Bunk
2007-08-27 22:32 ` Adam Belay
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070825001454.GA23622@redhat.com \
--to=davej@redhat.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=johnstul@us.ibm.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tilman@imap.cc \
--cc=trenn@suse.de \
--cc=venkatesh.pallipadi@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).