From owner-freebsd-current@FreeBSD.ORG Fri Mar 15 15:45:27 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 92BE4815; Fri, 15 Mar 2013 15:45:27 +0000 (UTC) (envelope-from uzimac@da3m0n8t3r.com) Received: from z.umatar.com (z.umatar.com [66.135.39.87]) by mx1.freebsd.org (Postfix) with ESMTP id 66D9F9AA; Fri, 15 Mar 2013 15:45:27 +0000 (UTC) Received: from z.umatar.com (localhost [127.0.0.1]) by z.umatar.com (8.14.5/8.14.3) with ESMTP id r2FFjQmT025303; Fri, 15 Mar 2013 08:45:26 -0700 (PDT) (envelope-from uzimac@da3m0n8t3r.com) Received: (from uzimac@localhost) by z.umatar.com (8.14.5/8.14.3/Submit) id r2FFjQh3025302; Fri, 15 Mar 2013 08:45:26 -0700 (PDT) (envelope-from uzimac@da3m0n8t3r.com) X-Authentication-Warning: z.umatar.com: uzimac set sender to uzimac@da3m0n8t3r.com using -f From: "Waitman Gobble" Subject: Re: reservation of n, n (3) failed To: John Baldwin Message-Id: <1363362326.25215@da3m0n8t3r.com> X-Originating-IP: 70.90.171.37 X-Mailer: Usermin 1.510 In-Reply-To: <201303150943.42474.jhb@freebsd.org> Date: Fri, 15 Mar 2013 08:45:26 -0700 (PDT) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="bound1363362326" Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 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, 15 Mar 2013 15:45:27 -0000 This is a multi-part message in MIME format. --bound1363362326 Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit John Baldwin wrote .. > On Thursday, March 14, 2013 1:41:04 am Waitman Gobble wrote: > > > > Hi, > > > > I swapped out the CPU on this machine today, I don't recall seeing these messages > previously: > > > > acpi0: reservation of 0, a0000 (3) failed > > acpi0: reservation of 100000, bfcd0000 (3) failed > > You can ignore those. acpi is trying to reserve the addresses used for RAM > as system resources, but the ram0 driver has already done so. > > -- > John Baldwin Hi, Thank you, I appreciate the info. -- Waitman Gobble San Jose California USA --bound1363362326--