From owner-freebsd-stable@FreeBSD.ORG Tue Mar 15 06:00:49 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 86A3E16A4CE for ; Tue, 15 Mar 2005 06:00:49 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 650D643D5A for ; Tue, 15 Mar 2005 06:00:49 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 5A99572DDB; Mon, 14 Mar 2005 22:00:49 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 5619672DD9; Mon, 14 Mar 2005 22:00:49 -0800 (PST) Date: Mon, 14 Mar 2005 22:00:49 -0800 (PST) From: Doug White To: Dan Ponte In-Reply-To: <20050312140717.GA43253@neptune.atopia.net> Message-ID: <20050314215920.B8240@carver.gumbysoft.com> References: <20050312140717.GA43253@neptune.atopia.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: stable@freebsd.org Subject: Re: ACPI errors on boot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Mar 2005 06:00:49 -0000 On Sat, 12 Mar 2005, Dan Ponte wrote: > I've been seeing lots of ACPI errors in my dmesg lately. They haven't > really affected functionality (yet!), but I'd like to see them resolved > nonetheless. I've googled all around, could not find a hint of a > solution. This machine is an ASUS CUSL2 motherboard with BIOS revision > 1009. Below is my dmesg. ASUS motherboards are known to have broken ACPI code so this isn't too suprising. > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.PX40.UAR2._STA] (Node 0xc15b8dc0), AE_NOT_EXIST This appears to be trying to get resource information for uart #2 (sio1). Since that port probes OK anyway its likely harmless. If you want to try to clear these up, try a BIOS update first (if available), then look for a replacement DSDT table. You can use the loader options described in acpi(4) to load the fixed table. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org