From owner-freebsd-current@FreeBSD.ORG Sun Feb 15 01:08:57 2004 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 0F54016A4CE for ; Sun, 15 Feb 2004 01:08:57 -0800 (PST) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 4436C43D1F for ; Sun, 15 Feb 2004 01:08:56 -0800 (PST) (envelope-from pilkis@gmx.net) Received: (qmail 26653 invoked by uid 65534); 15 Feb 2004 09:08:53 -0000 Received: from unknown (EHLO pilkishome) (62.68.63.42) by mail.gmx.net (mp017) with SMTP; 15 Feb 2004 10:08:53 +0100 X-Authenticated: #6832473 Message-ID: <015e01c3f3a3$56edf500$1e64a8c0@spotripoli.local> From: "Putinas" To: References: <20040214202424.C3256@carver.gumbysoft.com> Date: Sun, 15 Feb 2004 11:08:54 +0200 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="windows-1251"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2055 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2055 Subject: Re: ACPI-0438: *** Error: Looking up [\\_PR_.CPU0] in namespace, AE_NOT_FOUND 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, 15 Feb 2004 09:08:57 -0000 How bad is this thing ( AE_NOT_FOUND ) ? pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 1.0 on pci0 pcib1: could not get PCI interrupt routing table for \\_SB_.PCI0.P0P1 - AE_NOT_FOUND pci1: on pcib1 pcib2: at device 30.0 on pci0 ----- Original Message ----- From: "Doug White" To: "Martin Minkus" Cc: Sent: Sunday, February 15, 2004 6:25 AM Subject: Re: ACPI-0438: *** Error: Looking up [\\_PR_.CPU0] in namespace, AE_NOT_FOUND > On Sat, 14 Feb 2004, Martin Minkus wrote: > >> I've been getting this weird error message of late on newer current >> builds. > > Have you upgraded your BIOS recently? This is probably a bug in the > bytecode provided in the system BIOS. > > -- > Doug White | FreeBSD: The Power to Serve > dwhite@gumbysoft.com | www.FreeBSD.org > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > >