From owner-freebsd-current@FreeBSD.ORG Sun Nov 16 12:11:11 2003 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 4DAAF16A4CE for ; Sun, 16 Nov 2003 12:11:11 -0800 (PST) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id D223243FAF for ; Sun, 16 Nov 2003 12:11:10 -0800 (PST) (envelope-from nate@rootlabs.com) Received: (qmail 57546 invoked by uid 1000); 16 Nov 2003 20:11:11 -0000 Date: Sun, 16 Nov 2003 12:11:11 -0800 (PST) From: Nate Lawson To: Harald Schmalzbauer Message-ID: <20031116120622.O57495@root.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: acpi_cpu_idle panic (Was: Re: kernel panic with todays source) 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: Sun, 16 Nov 2003 20:11:11 -0000 The panic you see is a result of the new acpi_cpu driver, not ULE. In any case, it appears that acpi_cpu_idle is being called and trying to read one of the processor control registers before they are present. Please send me privately the output of: acpidump -t -d > harald-MachineType.asl As a workaround, please set this in loader.conf: debug.acpi.disable="cpu" That will allow you to get running and give me some time to look into this. Thanks, -Nate