From owner-freebsd-acpi@FreeBSD.ORG Wed Nov 9 05:07:25 2005 Return-Path: X-Original-To: acpi@freebsd.org 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 8CBE316A41F for ; Wed, 9 Nov 2005 05:07:25 +0000 (GMT) (envelope-from nate@root.org) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 42B0F43D49 for ; Wed, 9 Nov 2005 05:07:25 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.250] (ppp-71-139-0-107.dsl.snfc21.pacbell.net [71.139.0.107]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id jA957BDI016206 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 8 Nov 2005 21:07:14 -0800 Message-ID: <437183FA.80804@root.org> Date: Tue, 08 Nov 2005 21:07:06 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "M. Warner Losh" References: <20051108.213804.102936607.imp@bsdimp.com> In-Reply-To: <20051108.213804.102936607.imp@bsdimp.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: acpi@freebsd.org Subject: Re: acpi_perf X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Nov 2005 05:07:25 -0000 M. Warner Losh wrote: > A long time ago I disabled acpi_perf because it was causing a double > free panic. I'd forgotten that I'd done this until recently when I > noticed in the /boot/loader.conf file. I renabled it and now I see: > > cpu0: on acpi0 > acpi_perf0: on cpu0 > acpi_perf0: failed in PERF_STATUS attach > device_attach: acpi_perf0 attach returned 6 > acpi_perf0: on cpu0 > acpi_perf0: failed in PERF_STATUS attach > device_attach: acpi_perf0 attach returned 6 > acpi_throttle0: on cpu0 > acpi_lid0: on acpi0 > > I don't know if this happened before or not, but I was wondering what > people think the next step would be. Dump your ASL and look for what the _PCT method returns under your Processor object. It will reference two registers, the control and status regs. Post that ASL and we'll see why register setup is failing. It could be a collision with someone else who has grabbed the SMI port or it is not an IO or Memory-based register. -- Nate