From: Frans Pop <elendil@planet.nl>
To: Zhao Yakui <yakui.zhao@intel.com>
Cc: linux-acpi@vger.kernel.org
Subject: Re: Syntax errors in SSDT1 table of HP 2510p laptop
Date: Fri, 26 Sep 2008 06:52:20 +0200 [thread overview]
Message-ID: <200809260652.21929.elendil@planet.nl> (raw)
In-Reply-To: <1222400642.4023.187.camel@yakui_zhao.sh.intel.com>
On Friday 26 September 2008, Zhao Yakui wrote:
> Will you please try the latest kernel (2.6.27-rc6) and see whether the
> problem still exists?
Sorry that I did not make that clear, but I am already running with
current git (v2.6.27-rc7-94-gc0f4d6d).
> It seems that the problem is fixed by the following commit:
> commit 48feb3c419508487becfb9ea3afcc54c3eac6d80
The kernel errors listed in that commit log are rather different from what
I'm seeing.
Also, how could a commit in the kernel fix a broken ACPI table? No change
in the kernel can repair syntax errors that show up when you disassemble
and recompile the ACPI table itself, can it?
I thought using iasl as I did was the accepted way to uncover errors in a
system's ACPI tables.
I really think the problem is in the ACPI table in this case, not in the
kernel.
Cheers,
FJP
next prev parent reply other threads:[~2008-09-26 4:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-25 9:19 Syntax errors in SSDT1 table of HP 2510p laptop Frans Pop
2008-09-26 3:44 ` Zhao Yakui
2008-09-26 4:52 ` Frans Pop [this message]
2008-09-26 13:37 ` Moore, Robert
2008-09-26 16:08 ` iasl and SSDT disassembling limitations Henrique de Moraes Holschuh
2008-09-26 16:48 ` Moore, Robert
2008-09-30 8:46 ` Syntax errors in SSDT1 table of HP 2510p laptop Frans Pop
[not found] <3515468CA27A0F49917112E2ECF61E2108A535697F@pdsmsx502.ccr.corp.intel.com>
2008-10-07 5:33 ` Lin Ming
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=200809260652.21929.elendil@planet.nl \
--to=elendil@planet.nl \
--cc=linux-acpi@vger.kernel.org \
--cc=yakui.zhao@intel.com \
/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