ACPI errors at bit on Abit BP-6 mb (since 5.1) on 5.2RC

[Scott W]

Chad Leigh -- Shire.Net LLC wrote:

> Hi.
>
> I have been getting these errors at boot time on a dual CPU Abit 
> BP-6.   This has been happening since I converted this old system into 
> a test  system a while back with 5.1R.  It still happens with 5.2RC.  
> I have  not updated to 5.2R yet.  It still seems to run fine and 
> stably even  with the errors.
>
> What do these mean?
>
> Here is a dmesg
>
> Copyright (c) 1992-2004 The FreeBSD Project.
> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
>         The Regents of the University of California. All rights  
> reserved.
> FreeBSD 5.2-RC #1: Thu Jan  8 09:59:56 MST 2004
>     chad at nabiki.shire.net:/usr/obj/usr/src/sys/NABIKI-SMP


> [dmesg snipped]


>
> Mounting root from ufs:/dev/ad0s1a
>     ACPI-0438: *** Error: Looking up [\\_PR_.CPU0] in namespace,  
> AE_NOT_FOUND
> SearchNode 0xc54fd260 StartNode 0xc54fd260 ReturnNode 0
>     ACPI-1287: *** Error: , AE_NOT_FOUND
>     ACPI-0438: *** Error: Looking up [\\_PR_.CPU0] in namespace,  
> AE_NOT_FOUND
> SearchNode 0xc54fd260 StartNode 0xc54fd260 ReturnNode 0
>     ACPI-1287: *** Error: , AE_NOT_FOUND
>
I installed and ran fbsd 5.1 and current for a bit on a BP6, dual 
Cel-366.  Only problems I came across were:

1.  Flash the board to the lastest/BIOS.  This had cured a few issues 
when it was running Linux SMP previously.

2.  Enable the Intel MP spec in BIOS, 1.4 if available (no longer have 
the system so can't verify, but I believe it's a BIOS option even on the 
BP-6)

3.  If you're overclocking it, go back to the normal speed at least for 
the install.  I hadn't reloaded that system in so long I forgot they 
were 366MHz CPUs (they were overclocked to somewhere ~450MHz), and ran 
into all kinds of problems until I checked and then reset it back to the 
default...which was interesting, as the system had been successfully 
running Oracle on RH7.3 for some time previously in the same 
configuration...

Definitely never saw any similar messages as yours, but there's also a 
BP-6 motherboard issue some have come across- try googling for "BP-6 
problem" if all else fails, something about a (filtering?) cap being the 
wrong size...

Scott