From owner-freebsd-current@FreeBSD.ORG  Fri Mar 25 22:30:19 2005
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 5F58D16A4CE
	for <freebsd-current@freebsd.org>;
	Fri, 25 Mar 2005 22:30:19 +0000 (GMT)
Received: from harmony.village.org (rover.village.org [168.103.84.182])
	by mx1.FreeBSD.org (Postfix) with ESMTP id B3A7143D2F
	for <freebsd-current@freebsd.org>;
	Fri, 25 Mar 2005 22:30:18 +0000 (GMT)	(envelope-from imp@bsdimp.com)
Received: from localhost (warner@rover2.village.org [10.0.0.1])
	by harmony.village.org (8.13.3/8.13.1) with ESMTP id j2PMQOGb041224;
	Fri, 25 Mar 2005 15:26:24 -0700 (MST)
	(envelope-from imp@bsdimp.com)
Date: Fri, 25 Mar 2005 15:26:56 -0700 (MST)
Message-Id: <20050325.152656.19040116.imp@bsdimp.com>
To: shoesoft@gmx.net
From: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <1111770186.591.6.camel@something.pepperland>
References: <1111770186.591.6.camel@something.pepperland>
X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
cc: freebsd-current@freebsd.org
Subject: Re: panic: resource_list_add: resource entry is busy
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Mar 2005 22:30:19 -0000

In message: <1111770186.591.6.camel@something.pepperland>
            Stefan Ehmann <shoesoft@gmx.net> writes:
: acpi_perf0: <ACPI CPU Frequency Control> on cpu0
: acpi_perf0: failed in PERF_STATUS attach
: device_attach: acpi_perf0 attach returned 6
: >>> This happens with new kernel:
: >>> panic: resource_list_add: resource entry is busy

I've seen this too.  I added

hint.acpi_perf.0.disabled=1

to /boot/loader.conf and the problem disappeared.

Warner