From owner-freebsd-acpi@FreeBSD.ORG Tue May 11 11:45:35 2010 Return-Path: Delivered-To: freebsd-acpi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2C2A9106564A for ; Tue, 11 May 2010 11:45:35 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 002768FC08 for ; Tue, 11 May 2010 11:45:34 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id A18AF46B8C; Tue, 11 May 2010 07:45:34 -0400 (EDT) Received: from John-Baldwins-Macbook-Pro.local (localhost [IPv6:::1]) by bigwig.baldwin.cx (Postfix) with ESMTPA id 9F3478A021; Tue, 11 May 2010 07:45:33 -0400 (EDT) Message-ID: <4BE94364.6080707@FreeBSD.org> Date: Tue, 11 May 2010 07:45:40 -0400 From: John Baldwin User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228) MIME-Version: 1.0 To: Nate Lawson References: <4BE8E0F1.80405@root.org> In-Reply-To: <4BE8E0F1.80405@root.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Tue, 11 May 2010 07:45:33 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=4.2 tests=BAYES_00,NO_RELAYS autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: freebsd-acpi@FreeBSD.org, avatar Lin Subject: Re: About "acpi0: reservation of ... failed" message in `dmesg` 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: Tue, 11 May 2010 11:45:35 -0000 Nate Lawson wrote: > avatar Lin wrote: >> Our customers are concerned about the following messages in `dmesg` output. >> >> === >> acpi0: reservation of 0, a0000 (3) failed >> acpi0: reservation of 100000, bff00000 (3) failed >> === >> >> Please help to clarify this issue. >> >> Or , in other direction, where to find official document to convince >> our customers that these messages are ignorable ? > > It is related to the sysresource acpi memory objects. It means that > something was using the system resource before acpi allocated it. For > #1, that looks like lowmem up to the VGA range. For #2, it looks like > option ROMs. > > The BIOS has configured the devices beforehand so as long as everything > works, the msgs can be ignored. Actually, to handle non-ACPI systems and ACPI systems that do not list system memory in the system resource objects, I added a 'ram0' device which uses the SMAP table and allocates address space for all of memory to perform a similar function to ACPI system resource objects. Often this message triggers now because the ram0 device has claimed the resources before ACPI gets a chance. You can certainly ignore these messages. If you look in 'devinfo -ur' you will probably find that these resource ranges are allocated by the ram0 device. -- John Baldwin