From owner-freebsd-current@FreeBSD.ORG Fri Mar 25 19:43:58 2005 Return-Path: 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 C6DF716A4CE for ; Fri, 25 Mar 2005 19:43:58 +0000 (GMT) Received: from email.aon.at (warsl404pip8.highway.telekom.at [195.3.96.102]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF23443D49 for ; Fri, 25 Mar 2005 19:43:57 +0000 (GMT) (envelope-from shoesoft@gmx.net) Received: (qmail 1413 invoked from network); 25 Mar 2005 19:43:55 -0000 Received: from n750p004.dipool.highway.telekom.at ([212.183.103.164]) (envelope-sender ) by smarthub75.highway.telekom.at (qmail-ldap-1.03) with SMTP for ; 25 Mar 2005 19:43:55 -0000 From: Stefan Ehmann To: freebsd-current@FreeBSD.org In-Reply-To: <1111770186.591.6.camel@something.pepperland> References: <1111770186.591.6.camel@something.pepperland> Content-Type: text/plain Date: Fri, 25 Mar 2005 20:43:57 +0100 Message-Id: <1111779837.963.2.camel@taxman.pepperland> Mime-Version: 1.0 X-Mailer: Evolution 2.2.1.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Mar 2005 19:43:58 -0000 On Fri, 2005-03-25 at 18:03 +0100, Stefan Ehmann wrote: > After today's update I get this early on boot: > panic: resource_list_add: resource entry is busy > > It boots fine with ACPI disabled. Kernel from ~1 week ago doesn't panic > either. > > See at end of attached dmesg for detail. > > Sorry for no backtrace but it's quite annoying to transcribe it by hand. > If really needed, I can provide it of course. While trying to find the commit that caused the panic, I found it already has been reported here: http://lists.freebsd.org/pipermail/cvs-src/2005-March/043388.html It's still not fixed though (only a workaround is mentioned there).