Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932847AbXHYARO (ORCPT ); Fri, 24 Aug 2007 20:17:14 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1763466AbXHYAQq (ORCPT ); Fri, 24 Aug 2007 20:16:46 -0400 Received: from mx1.redhat.com ([66.187.233.31]:60014 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1761356AbXHYAQo (ORCPT ); Fri, 24 Aug 2007 20:16:44 -0400 Date: Fri, 24 Aug 2007 20:14:54 -0400 From: Dave Jones To: Andrew Morton Cc: Tilman Schmidt , linux-kernel@vger.kernel.org, Thomas Gleixner , john stultz , Andi Kleen , Len Brown , linux-acpi@vger.kernel.org, Thomas Renninger , Venkatesh Pallipadi Subject: Re: 2.6.23-rc3-mm1 Message-ID: <20070825001454.GA23622@redhat.com> Mail-Followup-To: Dave Jones , Andrew Morton , Tilman Schmidt , linux-kernel@vger.kernel.org, Thomas Gleixner , john stultz , Andi Kleen , Len Brown , linux-acpi@vger.kernel.org, Thomas Renninger , Venkatesh Pallipadi References: <20070822020648.5ea3a612.akpm@linux-foundation.org> <46CF695D.1020008@imap.cc> <20070824170702.a2c51084.akpm@linux-foundation.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070824170702.a2c51084.akpm@linux-foundation.org> User-Agent: Mutt/1.5.14 (2007-02-12) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1301 Lines: 28 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/