RELENG_6: ACPI-0698: *** Warning: Type override:

Xin LI delphij at gmail.com
Fri Nov 18 18:08:34 GMT 2005


Hi,

On 11/19/05, Ricardo A. Reis <ricardo_bsd at yahoo.com.br> wrote:
> Hi all,
>
>
>          Updating proxy server running 5.4, i resolve enable acpi,smp
> kernel  to use HTT.
[snip]
Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
>  Features2=0x400<CNTX-ID>
>  Hyperthreading: 2 logical CPUs

JFYI: disabling hyperthreading in BIOS could actually improve your performance.

[snip]
>  cpu0 (BSP): APIC ID:  0
>  cpu1 (AP): APIC ID:  1
>    ACPI-0698: *** Warning: Type override - [DEB_] had invalid type
> (Integer) for Scope operator, changed to (Scope)
>    ACPI-0698: *** Warning: Type override - [MLIB] had invalid type
> (Integer) for Scope operator, changed to (Scope)
>    ACPI-0698: *** Warning: Type override - [DATA] had invalid type
> (String) for Scope operator, changed to (Scope)
>    ACPI-0698: *** Warning: Type override - [SIO_] had invalid type
> (String) for Scope operator, changed to (Scope)
>    ACPI-0698: *** Warning: Type override - [LEDP] had invalid type
> (String) for Scope operator, changed to (Scope)
>    ACPI-0698: *** Warning: Type override - [GPEN] had invalid type
> (String) for Scope operator, changed to (Scope)
>    ACPI-0698: *** Warning: Type override - [GPST] had invalid type
> (String) for Scope operator, changed to (Scope)
>    ACPI-0698: *** Warning: Type override - [WUES] had invalid type
> (String) for Scope operator, changed to (Scope)
>    ACPI-0698: *** Warning: Type override - [WUSE] had invalid type
> (String) for Scope operator, changed to (Scope)
>    ACPI-0698: *** Warning: Type override - [SBID] had invalid type
> (String) for Scope operator, changed to (Scope)
>    ACPI-0698: *** Warning: Type override - [SWCE] had invalid type
> (String) for Scope operator, changed to (Scope)

This looks like a bug in either ACPICA or your BIOS.  Would you please
consider downloading a November snapshot of 7.0-CURRENT's disc1 and
try to boot it on your box to see if the problem persists?  Another
thing that is worthy to try is to update your BIOS to latest release.

BTW.  It might be good to cc' this to freebsd-acpi@ as well if you got
some findings.

Cheers,
--
Xin LI <delphij at delphij.net> http://www.delphij.net


More information about the freebsd-stable mailing list