Date: Mon, 21 Nov 2005 22:14:21 -0800 From: Nate Lawson <nate@root.org> To: Mike Tancsa <mike@sentex.net> Cc: freebsd-acpi@freebsd.org Subject: Re: work around for busted RS-482 ACPI ? (Long) Message-ID: <4382B73D.8030502@root.org> In-Reply-To: <6.2.3.4.0.20051121215854.0895cc28@64.7.153.2> References: <6.2.3.4.0.20051121215854.0895cc28@64.7.153.2>
next in thread | previous in thread | raw e-mail | index | archive | help
Mike Tancsa wrote:
> I like in theory the specs of this board, but I guess the busted ACPI is
> telling me to stay away. Its an MSI RS482M4-ILD mATX S939 RS482. The
> default boot panics with
>
> CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ (2193.63-MHz
> 686-class CPU)
> Origin = "AuthenticAMD" Id = 0x20fb1 Stepping = 1
>
> Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT>
>
> Features2=0x1<SSE3>
> AMD Features=0xe2500800<SYSCALL,NX,MMX+,<b25>,LM,3DNow+,3DNow>
> real memory = 1006436352 (959 MB)
> avail memory = 975667200 (930 MB)
> ACPI APIC Table: <A M I OEMAPIC >
> FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
> cpu0 (BSP): APIC ID: 0
> cpu1 (AP): APIC ID: 1
> nssearch-0397: *** Error: NsSearchAndEnter: Bad character in ACPI Name:
> 43005350
> dswload-0381: *** Error: Looking up [0x43005350] (NON-ASCII)
> in namespace, AE_BAD_CHARACTER
> psparse-0714 [09] PsParseLoop : During name lookup/catalog,
> AE_BAD_CHARACTER
> tbxface-0204: *** Error: AcpiLoadTables: Could not load namespace:
> AE_BAD_CHARACTER
> tbxface-0213: *** Error: AcpiLoadTables: Could not load tables:
> AE_BAD_CHARACTER
> ACPI: table load failed: AE_BAD_CHARACTER
> utalloc-1069 [04] UtDumpAllocations : No outstanding allocations.
> MADT: ACPI Startup failed with AE_BAD_CHARACTER
> Try disabling either ACPI or apic support.
> panic: Using MADT but ACPI doesn't work
The issue is that there's a NUL ('\0') in the namespace, at least
referenced from the MADT. The string is "C\0SP". I think it would help
if we could hack AcpiLoadTables to overwrite the \0 with a 'X' character
instead of bailing out, then find where the X is. Ultimately, it's
probably better to just overwrite with '_' than to crash out.
--
Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4382B73D.8030502>