From owner-freebsd-acpi@FreeBSD.ORG Tue Jul 13 17:58:31 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C3C7916A4CE for ; Tue, 13 Jul 2004 17:58:31 +0000 (GMT) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7F33243D2F for ; Tue, 13 Jul 2004 17:58:31 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.34] (adsl-63-195-111-154.dsl.snfc21.pacbell.net [63.195.111.154]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id i6DHwTrb025349 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 13 Jul 2004 10:58:30 -0700 Message-ID: <40F3BDDD.3070408@root.org> Date: Tue, 13 Jul 2004 10:47:57 +0000 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.6 (X11/20040518) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Andrea Campi References: <20040706084203.GB19813@webcom.it> <20040713122312.GA47428@webcom.it> <20040713234143.051ddd3e.taku@tackymt.homeip.net> <20040713145552.GB47428@webcom.it> In-Reply-To: <20040713145552.GB47428@webcom.it> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-acpi@freebsd.org Subject: Re: [FOUND}: CPU Cx states not working with recent kernel on Thinkpad X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jul 2004 17:58:31 -0000 Andrea Campi wrote: > Hi, > > On Tue, Jul 13, 2004 at 11:41:43PM +0900, Taku YAMAMOTO wrote: > >>I suspect it's because acpi_timer0 gets attached and sits on >>not-yet-managed resources before acpi_sysresource0 reserves >>resources for later use. >> >>We can confirm that by temporarily disabling acpi_timer by >>debug.acpi.disabled="timer" to see the working acpi_cpu. > > > That's confirmed; disabling the timer fixed the issue, and devinfo > confirms what you said: I just committed a fix. We now call device_identify routines after the namespace walk. Thanks for the helpful info. -- -Nate