Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752674AbWAHSSn (ORCPT ); Sun, 8 Jan 2006 13:18:43 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752672AbWAHSSn (ORCPT ); Sun, 8 Jan 2006 13:18:43 -0500 Received: from fmr14.intel.com ([192.55.52.68]:29119 "EHLO fmsfmr002.fm.intel.com") by vger.kernel.org with ESMTP id S1752671AbWAHSSm convert rfc822-to-8bit (ORCPT ); Sun, 8 Jan 2006 13:18:42 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Subject: RE: 2.6.15-mm2 Date: Sun, 8 Jan 2006 13:18:29 -0500 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: 2.6.15-mm2 Thread-Index: AcYUTsDFLOzJOE8GQfafuaCXHtpDRAAMAATw From: "Brown, Len" To: "Andrew Morton" , "Brice Goglin" Cc: , X-OriginalArrivalTime: 08 Jan 2006 18:18:32.0261 (UTC) FILETIME=[EE925F50:01C6147F] Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 836 Lines: 26 >> 2.6.15 and 2.6.15-git3 both don't show any of these issues. >> Did acpi and cpufreq get merged after -git3 ? >> > >Well whatever bug it is, it's in Linus's tree now. Happens for me too. > >I traced the failure down as far as acpi_processor_get_performance_info(), >where it's failing here: > > status = acpi_get_handle(pr->handle, "_PCT", &handle); > if (ACPI_FAILURE(status)) { > ACPI_DEBUG_PRINT((ACPI_DB_INFO, > "ACPI-based processor >performance control unavailable\n")); > return_VALUE(-ENODEV); > } No, acpi was not merged after 2.6.15 -- see if cpufreq changed. -Len - 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/