From: glen martin <lists@locutory.org>
To: "Brown, Len" <len.brown@intel.com>
Cc: linux-acpi@vger.kernel.org
Subject: Re: no /proc/acpi, trying to dump dsdt to a file
Date: Wed, 29 Mar 2006 11:57:11 -0800 [thread overview]
Message-ID: <442AE697.5040809@locutory.org> (raw)
In-Reply-To: <CFF307C98FEABE47A452B27C06B85BB60B8170@hdsmsx411.amr.corp.intel.com>
the nssearch patch certainly bypasses the first level problem. Here's
the dmesg output with that patch applied.
<>
tbxface-0109 [02] load_tables : ACPI Tables successfully acquired
nssearch-0311: *** Error: ns_search_and_enter: Bad character in ACPI
Name: 43035350
nssearch-0311: *** Error: ns_search_and_enter: Bad character in ACPI
Name: 43035350
Parsing all Control
Methods:.....................................................................
.................................................................................................
.................................................................................................
.........
Table [DSDT](id 0005) - 815 Objects with 73 Devices 272 Methods 18 Regions
ACPI Namespace successfully loaded at root c05abe7c
evxfevnt-0091 [03] enable : Transition to ACPI mode
successful
<>
Now /proc/acpi/dsdt is present! However:
<>
test A8N # cat /proc/acpi/dsdt > dsdt1.dat
test A8N # iasl -d dsdt1.dat
Intel ACPI Component Architecture
AML Disassembler version 20060127 [Mar 29 2006]
Copyright (C) 2000 - 2006 Intel Corporation
Supports ACPI Specification Revision 3.0a
Loading Acpi table from file dsdt1.dat
Acpi table [DSDT] successfully installed and loaded
Pass 1 parse of [DSDT]
test A8N # more dsdt1.dsl
ACPI Error (nssearch-0405): Bad character in ACPI Name: 43035350 [20060127]
ACPI Error (dswload-0393): [0x43035350] (NON-ASCII) Namespace lookup
failure, AE_BAD_CHARACTER
ACPI Exception (psloop-0347): AE_BAD_CHARACTER, During name
lookup/catalog [20060127]
Could not parse ACPI tables, AE_BAD_CHARACTER
<>
I also tried acpidump (thanks for the suggestion), which gave me:
<>
test acpidump # ./acpidump -t DSDT -o dsdt.hex
Wrong checksum for generic table!
<>
Brown, Len wrote:
>>-----Original Message-----
>>From: Brown, Len
>>Sent: Wednesday, March 29, 2006 2:04 PM
>>To: 'glen martin'; linux-acpi@vger.kernel.org
>>Subject: RE: no /proc/acpi, trying to dump dsdt to a file
>>
>>You can dump your ACPI tables with acpidump, no matter if you
>>are booted in ACPI mode or not. Get the latest from pmtools here:
>>
>>http://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/utils/
>>
>>/DSDT.aml not found.
>>
>>
>>>tbxface-0109 [02] load_tables : ACPI Tables successfully acquired
>>>nssearch-0311: *** Error: ns_search_and_enter: Bad character in ACPI
>>>Name: 43035350
>>>dswload-0292: *** Error: Looking up [0x43035350] (NON-ASCII)
>>>in namespace, AE_BAD_CHARACTER
>>> psloop-0287 [09] ps_parse_loop : During name lookup/catalog,
>>>AE_BAD_CHARACTER
>>>tbxface-0115: *** Error: acpi_load_tables: Could not load namespace:
>>>AE_BAD_CHARACTER
>>>tbxface-0123: *** Error: acpi_load_tables: Could not load tables:
>>>AE_BAD_CHARACTER
>>>ACPI: Unable to load the System Description Tables
>>>
>>>
>>>Any suggestions?
>>>
>>>
>>Replace the non-ascii character with an ascii one.
>>There is a patch about to work around this -- let me find it...
>>
>>
>
>Please try the test patch here:
>https://bugzilla.novell.com/show_bug.cgi?id=147621#c22
>-
>To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
>
next prev parent reply other threads:[~2006-03-29 19:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-29 19:11 no /proc/acpi, trying to dump dsdt to a file Brown, Len
2006-03-29 19:57 ` glen martin [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-29 21:05 Moore, Robert
2006-03-29 21:15 ` glen martin
2006-03-29 20:02 Moore, Robert
2006-03-29 20:27 ` glen martin
2006-03-29 19:05 Moore, Robert
2006-03-29 19:53 ` glen martin
2006-03-29 19:04 Brown, Len
2006-03-29 17:56 Moore, Robert
2006-03-29 18:49 ` glen martin
2006-03-29 17:50 glen martin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=442AE697.5040809@locutory.org \
--to=lists@locutory.org \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox